Wireshark-bugs: [Wireshark-bugs] [Bug 5953] Throughput shows incorrect value when packet is capp
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 30 May 2011 01:17:27 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5953

--- Comment #3 from Sake <sake@xxxxxxxxxx> 2011-05-30 01:17:21 PDT ---
(In reply to comment #2)
> (In reply to comment #1)
> > Can you be a little more explicit? What numbers are you exactly referring to?
> 
> The throughput numbers in the summary field shows incorrect values for the
> traffic captured when the packet size is truncated during capture (in
> comparison with traffic when packet sizes are not truncated).

I just tried wireshark 1.4.6 and it shows the same bandwidth for a capped and
non-capped file (I used an uncapped file and capped it with editcap).

So if you see different results, it's because the content of the files is
really different in other ways.

Could you capture the traffic of a transfer of 10MB twice (once with snaplength
128 and once with full frames) and then post the output of "capinfos <files>"
here?

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