Subject: Re: A simple TCP/socket/port question
To: VaX#n8 <firstname.lastname@example.org>
From: Perry E. Metzger <email@example.com>
Date: 07/03/1996 11:47:19
> When a server or inetd forks off an individual process (say, uucpd) to
> deal with a particular client, I vaguely recall reading somewhere that
> although listening for requests is done on a well-known port, when the
> process accepts on the socket, it gets a different, higher-numbered port
> to work on.
I don't know how you got that impression.
> If this is not the case, how does the kernel distinguish messages going to
> different uucpd's (or, if uucp is a bad example, ftpd command channels)
> running simultaneously?
They are talking on different sockets?
(Don't forget that a socket is a 4-tuple
[port-1, host-addr-1, port-2, host-addr-2]
and not a one sided thing.)