How does that tcp traffic work

[Bliss, Aaron]

Can you send me some references on the Internet to look at?  Thanks very
much for getting back to me.

Aaron 

-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Burke, Thomas G.
Sent: Friday, August 04, 2006 11:07 AM
To: General Red Hat Linux discussion list
Subject: RE: How does that tcp traffic work

The server will also pick an available port, otherwise it theo ther
listening webserver processes would not be able to listen for incoming
requests. 

-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of Bliss, Aaron
Sent: Friday, August 04, 2006 10:44 AM
To: General Red Hat Linux discussion list
Subject: How does that tcp traffic work

I know this is a bit of a networking question more than a redhat
question, however I'm sure you guys will be able to explain this to me;
I'm trying to understand exactly how this works, and have not been able
to find any solid authority on the subject; I understand the concept of
ports, well know ports, and part of the initial 3 way handshake of a new
tcp session; My question is, does the initial receiving host of a
session (usually a server) use the port that it's listening for the tcp
session, or does it negotiate a port number that is not in use like the
client does?  For example, host A is a client, host B is a webserver
listening on port 80; host A wants some data from host B's port 80; lets
say host A wants to use port 6785; will the tcp session then use port
6785 for host A and port 80 for host B, or will they also pick an
available port from host B as well; if port 80 is used, how are multiple
sessions possible; i.e. how can the host B serve up more web traffic if
port 80 is busy?  Thanks for your help.

Aaron

Confidentiality Notice:
The information contained in this electronic message is intended for the
exclusive use of the individual or entity named above and may contain
privileged or confidential information.  If the reader of this message
is not the intended recipient or the employee or agent responsible to
deliver it to the intended recipient, you are hereby notified that
dissemination, distribution or copying of this information is
prohibited.  If you have received this communication in error, please
notify the sender immediately by telephone and destroy the copies you
received.


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list