Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We all know that a TCP socket is identified by a four tuple entry:
src ip,
dest ip,
src port
dest port
TCP does the job of Multiplexing and Demultiplexing the Data from/to differnt processes running on the host.
In case of Demultiplexing, Destination IP information is there only in IP Headers. How come Dest IP is read by Transport Layer (TCP)?
Plz explain I m very much confused?
What is called
TCPin this context, is in reallityTCP/IPas in TCP over IP (UDP/IPis the same thing). In fact, [TC|UD]P and IP are extremly interwoven codewise in all major current socket implementations.The socket itself works from the IP layer upward, thus it has the Destination IP info, only the socket protocol handler specialises this to TCP. So by calling
(Or its equivalents in other languages) you will create an IP socket (first parameter), that uses TCP (3rd parameter). This implies, that the socket has the IP information as well as the TCP info,