Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 5953] Throughput shows incorrect value when packet is capp

Date: Fri, 1 Jul 2011 20:26:15 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5953

Chris Maynard <christopher.maynard@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Major                       |Normal

--- Comment #4 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-07-01 20:26:13 PDT ---
I tried to reproduce the problem using 2 methods:

First, I captured ~10MB traffic, saved the packets to a file (file.pcap), noted
the throughput, ran "editcap -s 100 file.pcap file_snap100.pcap", opened that
file and compared the throughput of the capped file with the original file.  No
difference.

Second, I transferred a ~20MB file, capturing the transfer with Wireshark w/out
specifying a snaplen, noted the throughput, then repeated the test with a
snaplen of 100.  The throughput was very similar, as expected. 

I ran these tests with trunk-1.4 and trunk, but on a 32-bit Windows XP SP3
system.  I don't have access to an x86-64 Windows 7 platform.

@Raghav, are you able to test on a 32-bit platform?

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