Prev: Wireless network problem.
Next: static dns entry
From: Cristiano on 30 Dec 2009 19:25
I see that many packets captured with Wireshark have a wrong checksum:
Checksum: 0x38ae [incorrect, should be 0xb197 (maybe caused by "TCP checksum
offload"?)].
Is that a problem?

Thanks
Cristiano


From: John Wunderlich on 30 Dec 2009 21:15
"Cristiano" <cristiano.pi(a)NSquipo.it> wrote in
news:4b3bef70$1(a)news.x-privat.org:

> I see that many packets captured with Wireshark have a wrong
> checksum: Checksum: 0x38ae [incorrect, should be 0xb197 (maybe
> caused by "TCP checksum offload"?)].
> Is that a problem?

Not usually a problem. Wireshark views packets as they are sent
to/from the NIC. Most NICs have an option that the NIC itself will
insert the checksum as the packet goes out instead of making the TCP
stack pre-calculate it and insert it (i.e. the job of inserting
checksum has been "offloaded" to the NIC). See the Advanced settings
in the device manager for your NIC for the offload option. If you
view the same packet with Wireshark from the destination computer on
the network, you will probably see a correct checksum.

HTH,
John

 | 
Pages: 1
Prev: Wireless network problem.
Next: static dns entry