Wireshark-bugs: [Wireshark-bugs] [Bug 10687] New: Feature Request: Bad Checksum 0x00000000
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 10 Nov 2014 15:04:54 +0000
Bug ID 10687
Summary Feature Request: Bad Checksum 0x00000000
Product Wireshark
Version unspecified
Hardware All
OS Windows 7
Status UNCONFIRMED
Severity Enhancement
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter sscheetz@parker.com 

Build Information:
Version 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)
--
Why is it in this day and age that wireshark is still telling me that an
Ethernet/TCP/UDP checksum of 0x00000000 is an error? Documentation right from
the wireshark website says it has to do with checksum offloading and I need to
change a setting in wireshark to stop validating checksums if it bothers me.
Why doesn't wireshark automatically see 0x00000000 and mark it as a Note or
less in the expert infos so if there is actually a checksum error it doesn't
get missed? I do realize I can create a display filter for this, I just feel I
shouldn't have to. I mean this in the best possible way. I have never had a
checksum of 0x00000000 actually turn out to be an issue, but if it actually was
calculated wrong I want to know.

You are receiving this mail because:
  • You are watching all bug changes.