| Bug ID |
10535
|
| Summary |
Incorrect average packet size
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)
Copyright 1998-2014 Gerald Combs <[email protected]> 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.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.1.22, with Gcrypt 1.6.0,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Sep 16 2014),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.1.22, Gcrypt 1.6.0, without AirPcap.
Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz, with 4053MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
>From https://ask.wireshark.org/questions/36821/incorrect-average-packet-size:
In the Statistics -> Packet Lengths command, the Average Packet Length appears
to be consistently reported as twice its true value. Take any trace of your own
and check it out -- especially if you're filtering the trace down to a small
number of frames displayed.
The Statistics->Summary window will show one value for the average size of the
displayed packets, and it'll be correct. The Statistics -> Packet Lengths
window will show twice the value, and it'll be wrong. And it'll be nonsense
compared to the histogram data (counts/sizes by bin).
For example, open
http://wiki.wireshark.org/SampleCaptures?action="">
and filter by (frame.number <= 6).
The "Displayed" column of Statistics->Summary shows 6 packets averaging 85
bytes, which is correct (85.3, actually). However, the Statistics->Packet
Length menu says that these 6 packets have an average length of 170.7 -- twice
as much, allowing for rounding. And read the rest of the output for this
command ... it shows that there are 2 packets in the 40-79 byte bin and 4
packets in the 80-159 bin, which is correct, so its output that the average is
170.7 is clearly inconsistent.
You are receiving this mail because:
- You are watching all bug changes.