Wireshark-bugs: [Wireshark-bugs] [Bug 12338] New: 802.11 conversation direction is mixed up
| Bug ID |
12338
|
| Summary |
802.11 conversation direction is mixed up
|
| Product |
Wireshark
|
| Version |
2.0.2
|
| Hardware |
x86-64
|
| OS |
Mac OS X 10.11
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
michele@pittoni.org
|
Build Information:
Version 2.0.2 (v2.0.2-0-ga16e22e from master-2.0)
Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.5, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
with
Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
with QtMultimedia, without AirPcap.
Running on Mac OS X 10.11.4, build 15E65 (Darwin 15.4.0), with locale C, with
libpcap version 1.5.3 - Apple version 54, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0.
Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz (with SSE4.2)
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
I'm analysing a trace file where I have an Access Point (e.g.
aa:aa:aa:aa:aa:aa, let's call it AA for short) and a station
(bb:bb:bb:bb:bb:bb, or BB). BB is downloading data through the AP.
The I/O graph, setting up a filter for 'wlan.sa == AA && wlan.da == BB' and one
for the opposite direction ('wlan.sa == BB && wlan.da == AA'), shows me what I
expect: ~40 Mb/s from AA to BB, ~2 Mb/s from BB to AA.
The 802.11 conversations list, however, tells me the exact opposite: ~7 KB from
AA to BB and ~2.2 MB from BB to AA over the whole duration of the trace.
I get the same results from the conversation list in Wireshark QT and in
tshark, so it's probably not a display problem.
You are receiving this mail because:
- You are watching all bug changes.
