Can We Handle both UDP and TCP requests on same port ??? ...

<< Back to: [comp.unix.programmer] Unix-socket-faq for network programming

Answer by mazx
Submitted on 3/15/2006
Rating: Not yet rated	Rate this answer:
Ports may be viewed as attachment points for network connections. If an application wants to offer a certain service, it attaches itself to a port and waits for clients (this is also called listening on the port). A client who wants to use this service allocates a port on its local host and connects to the server's port on the remote host. The same port may be open on many different machines, but on each machine only one process can open a port at any one time. An important property of ports is that once a connection has been established between the client and the server, another copy of the server may attach to the server port and listen for more clients. This property permits, for instance, several concurrent remote logins to the same host, all using the same port 513. TCP is able to tell these connections from one another because they all come from different ports or hosts. For example, if you log in twice to quark from erdos, the first rlogin client will use the local port 1023, and the second one will use port 1022. Both, however, will connect to the same port 513 on quark. The two connections will be distinguished by use of the port numbers used at erdos. This example shows the use of ports as rendezvous points, where a client contacts a specific port to obtain a specific service. In order for a client to know the proper port number, an agreement has to be reached between the administrators of both systems on the assignment of these numbers. For services that are widely used, such as rlogin, these numbers have to be administered centrally. This is done by the IETF (Internet Engineering Task Force), which regularly releases an RFC titled Assigned Numbers (RFC-1700). It describes, among other things, the port numbers assigned to well-known services. Linux uses a file called /etc/services that maps service names to numbers. It is worth noting that although both TCP and UDP connections rely on ports, these numbers do not conflict. This means that TCP port 513, for example, is different from UDP port 513. In fact, these ports serve as access points for two different services, namely rlogin (TCP) and rwho (UDP).

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: [comp.unix.programmer] Unix-socket-faq for network programming

[ Home | FAQ-Related Q&As | General Q&As | Answered Questions ]

Question by hari
Submitted on 11/10/2003
Related FAQ: [comp.unix.programmer] Unix-socket-faq for network programming
Rating:	Rate this question:
Can We Handle both UDP and TCP requests on same port ???

Answer by Rahul Jadhav
Submitted on 11/4/2004
Rating: Not yet rated	Rate this answer:
Hi Hari, Yes one can have both UDP and TCP requests on same port as each connection is identified by ( source IP ,Destination IP, Source Port, Destination Port, PROTOCOL) as protocol can be TCP or UDP both connections can be differentiated. -Rahul Jadhav

Answer by jalves
Submitted on 8/11/2005
Rating: Not yet rated	Rate this answer:
Yes you can!

Answer by smartass
Submitted on 5/9/2006
Rating: Not yet rated	Rate this answer:
maybe.

Answer by mushi
Submitted on 12/28/2006
Rating: Not yet rated	Rate this answer:
i dont know!?? but ide like to tho

Your name or nickname:
If you'd like to create a new account or access your existing account, put in your password here:
Your answer: