Wireshark-bugs: [Wireshark-bugs] [Bug 8629] New: bad tcp checksum not detected
Date: Sun, 05 May 2013 16:18:29 +0000
Bug ID 8629
Summary bad tcp checksum not detected
Classification Unclassified
Product Wireshark
Version 1.8.6
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter dennisolvany@gmail.com

Created attachment 10718 [details]
packet with bad checksum

Build Information:
Version 1.8.6 (SVN Rev 48142 from /trunk-1.8)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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 (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, 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, without Kerberos, with GeoIP, with PortAudio
V19-devel (built Mar  6 2013), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, 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.

Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Packet was captured with Cisco NAM appliance, hence no checksum offloading. Ran
the same packet through Wireshark and tcpdump. TCP checksum validation results
differed as follows.

Wireshark -- Bad Checksum: False

tcpdump -- 00:45:32.590943 IP (tos 0x0, ttl 50, id 183, offset 0, flags [DF],
proto TCP (6), length 1420)
    service.ariba.com.https > 10.31.46.245.54645: Flags [.], cksum 0x0000
(incorrect -> 0xfffe), seq 1225261072:1225262452, ack 3059077717, win 8295,
length 1380


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