- Unix Socket - Summary
- Unix Socket - Client Example
- Unix Socket - Server Example
- Unix Socket - Helper Functions
- Unix Socket - Core Functions
- Unix Socket - IP Address Functions
- Unix Socket - Network Byte Orders
- Unix Socket - Ports and Services
- Unix Socket - Structures
- Unix Socket - Client Server Model
- Unix Socket - Network Host Names
- Unix Socket - Network Addresses
- Unix Socket - What is a Socket?
- Unix Socket - Home
Unix Socket Useful Resources
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
Unix Socket - Ports and Services
When a cpent process wants to a connect a server, the cpent must have a way of identifying the server that it wants to connect. If the cpent knows the 32-bit Internet address of the host on which the server resides, it can contact that host. But how does the cpent identify the particular server process running on that host?
To resolve the problem of identifying a particular server process running on a host, both TCP and UDP have defined a group of well-known ports.
For our purpose, a port will be defined as an integer number between 1024 and 65535. This is because all port numbers smaller than 1024 are considered well-known -- for example, telnet uses port 23, http uses 80, ftp uses 21, and so on.
The port assignments to network services can be found in the file /etc/services. If you are writing your own server then care must be taken to assign a port to your server. You should make sure that this port should not be assigned to any other server.
Normally it is a practice to assign any port number more than 5000. But there are many organizations who have written servers having port numbers more than 5000. For example, Yahoo Messenger runs on 5050, SIP Server runs on 5060, etc.
Example Ports and Services
Here is a small pst of services and associated ports. You can find the most updated pst of internet ports and associated service at
.Service | Port Number | Service Description |
echo | 7 | UDP/TCP sends back what it receives. |
discard | 9 | UDP/TCP throws away input. |
daytime | 13 | UDP/TCP returns ASCII time. |
chargen | 19 | UDP/TCP returns characters. |
ftp | 21 | TCP file transfer. |
telnet | 23 | TCP remote login. |
smtp | 25 | TCP email. |
daytime | 37 | UDP/TCP returns binary time. |
tftp | 69 | UDP trivial file transfer. |
finger | 79 | TCP info on users. |
http | 80 | TCP World Wide Web. |
login | 513 | TCP remote login. |
who | 513 | UDP different info on users. |
Xserver | 6000 | TCP X windows (N.B. >1023). |
Port and Service Functions
Unix provides the following functions to fetch service name from the /etc/services file.
struct servent *getservbyname(char *name, char *proto) − This call takes service name and protocol name, and returns the corresponding port number for that service.
struct servent *getservbyport(int port, char *proto) − This call takes port number and protocol name, and returns the corresponding service name.
The return value for each function is a pointer to a structure with the following form −
struct servent { char *s_name; char **s_apases; int s_port; char *s_proto; };
Here is the description of the member fields −
Attribute | Values | Description |
---|---|---|
s_name | http | It is the official name of the service. For example, SMTP, FTP POP3, etc. |
s_apases | ALIAS | It holds the pst of service apases. Most of the time, it will be set to NULL. |
s_port | 80 | It will have the associated port number. For example, for HTTP, it will be 80. |
s_proto |
TCP UDP |
It is set to the protocol used. Internet services are provided using either TCP or UDP. |