Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 7759] New: When NIC calculates IPv4 header checksum, the packet is marked bad

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7759

           Summary: When NIC calculates IPv4 header checksum, the packet
                    is marked bad
           Product: Wireshark
           Version: 1.8.2
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: meckschlager@xxxxxxxxxxxx


Build Information:
Version 1.8.2 

Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Sep 10 2012), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap,  from the
PortableApps U3 device in drive C:.

Built using Microsoft Visual C++ 9.0 build 30729
--
All Packets that get sent via my NIC Intel 82567 have IP checksum 0 because the
card itself calculates the header checksum.

Now wireshark marks all those packets bad, because of the "bad" checksum. 

I've written a little patch that I'll attach.

Cheers

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.