Home > other > Caught found abnormal part of the TCP packet how to return a responsibility?
Caught found abnormal part of the TCP packet how to return a responsibility?
Time:09-18
With wireshark caught under the win10 found abnormal part of the TCP packets, such as the package: 1, the source MAC address (router), such as the router LAN port MAC is 123456, but the display is 654321, only part of this is 2, TCP checksum error, but the application layer showed no abnormalities, simple observation after that to get rid of the last two bytes 0 is normal, is exactly what happened? Should not be the problem of network card, have a check and the normal TCP packets, the network connection is normal,
CodePudding user response:
May be the cable aging or loose
CodePudding user response:
Here the checksum has three, one is the nic itself can help you calculate the checksum, protocol stack is a calculates, another is wireshark to calculate, if it is to the network card, the packet is only added checksum before nic to outgoing, but wireshark, scratching the package is in the card before sending, so that the bag of the checksum and wireshark is certainly not consistent, the network is normal, but caught found TCP checksum wrong package must be the machine sent out the package, because TCP is mandatory checksum, so foreign TCP packet checksum error, wireshark can hold to, but will be dropped by the protocol stack,