Wireshark-bugs: [Wireshark-bugs] [Bug 4965] New: Wrong calculation of the field "tcp.analysis.by
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 1 Jul 2010 12:35:38 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4965

           Summary: Wrong calculation of the field
                    "tcp.analysis.bytes_in_flight"
           Product: Wireshark
           Version: 1.2.9
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: stefaan.pouseele@xxxxxxxxx


Created an attachment (id=4869)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=4869)
capture file and excel sheet to illustrate the problem

Build Information:
Version 1.2.9 (SVN Rev 33171)

Copyright 1998-2010 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 with GTK+ 2.16.6, (32-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.0, with Lua 5.1, with GnuTLS 2.8.5, with Gcrypt 1.4.5,
with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Jun  8 2010),
with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

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

Check the man page and http://www.wireshark.org for more information.
--
Hi, 

when examining the field "tcp.analysis.bytes_in_flight" in Wireshark Version
1.2.9 (SVN Rev 33171) it seems Wireshark doesn't always calculate the correct
value. 

Attached you'll find a capture file and an excel sheet derived from it to
illustrate many occurrence of the wrong calculation. In the excel sheet I added
the column L == "Should be" with the manual calculated values. 

The capture file was analyzed on a Windows XP SP3 with all the latest Microsoft
updates.

Best Regards,
Stefaan

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