![]() So,Is there any veteran could give me an understandable answer. (4)Focus on No.14 and No.18,I also have no idea about these kind of packets that came from client 80.65. TCP is used in conjunction with IP in order to maintain a connection between the sender and the target and to ensure packet order. (2)No.4 means a message from my client application.(just like a login message req) (3)Focus on No.5 and No.7,actually my server application doesn't send these packets and only send No.6 to reply the No.4's login req. It was developed by the United States Department of Defense to enable the accurate and correct transmission of data between devices. Hi,you guys should have a look on this picture:(server 80.77 is linux,client 80.65 is WindowsXp) (1)surely,No.1,No.2 and No.3 mean TCP three-way handshaking. The TCP/IP model is the default method of data communication on the Internet. This is not connection based which means that one program can send a load of packets to. Application data transmission stops sending packets to the other side, while this side acknowledges FIN packet with an FIN-ACK. ![]() I determined the 60 bytes are from: 20 bytes TCP header + 20 bytes IP header + 14 bytes Ethernet + 6 bytes Trailerĭo these packets belong to the TCP/IP protocol? If so, what's their purpose? and why are they sent so frequently? (perhaps to maintain or check the connection between server and clients) UDP is also a protocol used in message transport or transfer. After the TCP connection between server and client establishes, I'm seeing a lot of TCP packets with no length like the one below, where 172.16.80.65 is the client and 172.16.178.77 is the server: 70 1.064245 172.16.80.65 172.16.178.77 TCP cvspserver > 60000 Seq=1112 Ack=33028 Win=65535 Len=0ĭetail:Frame 74 (60 bytes on wire, 60 bytes captured)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |