![]() If this is the case, you can eliminate the error display in one of two ways:ĭisable TCP checksum offload in the NIC driver. In this case, the checksum isn't really bad, and the error is cosmetic. ![]() The correct checksum is calculated before the packet is put on the wire. Wireshark sees the packet before it's passed to the NIC driver, so the checksum has not yet been calculated, which results in the error. When TCP checksum offload is enabled, calculation of the TCP checksum is done by the NIC driver software, rather than by the computer's CPU. ![]() ![]() If you are capturing on one of the end hosts involved in the communication, then the bad checksums are probably caused by TCP checksum offload. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |