https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4042
Bill Meier <wmeier@xxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Bill Meier <wmeier@xxxxxxxxxxx> 2009-09-22 18:29:24 PDT ---
(In reply to comment #0)
> --
> TCP shows bad checksum
>
I'm suspecting "TCP checksum ofloading"...
1. All and only the packets going from 192.168.... to 10.17....
with a non-zero TCP payload are marked as having "bad checksums".
2. The value of the TCP supposed checksum in each of the frames is
*highly correlated* with the length of the TCP payload for that frame.
"TCP checksums": d53f/d340 packets with TCP length 94
d533/d534 .............. 82
and soon.
Was the capture done on the node with address 192.168.... ?
IMHO this not a bug in Wireshark.
Please see:
http://www.wireshark.org/docs/wsug_html_chunked/ChAdvChecksums.html
http://wiki.wireshark.org/CaptureSetup/Offloading
I'm marking this as Invalid.
Please feel free to reopen this if you disagree.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
