Wireshark-bugs: [Wireshark-bugs] [Bug 12123] New: Guard Interval is not consistent between Radio
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 15 Feb 2016 10:33:53 +0000
Bug ID 12123
Summary Guard Interval is not consistent between Radiotap & wlan_radio
Product Wireshark
Version 2.1.x (Experimental)
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 thomas.baudelet@gmail.com 

Created attachment 14326 [details]
2 packets with values inverted Long & Short for radiotap & wlan_radio

Build Information:
Version 2.1.0-1833-g35ef16b (v2.1.0rc0-1833-g35ef16b from unknown)

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.3, build 15D21 (Darwin 15.3.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) i5-4278U CPU @ 2.60GHz (with SSE4.2)

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).

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

Check the man page and http://www.wireshark.org for more information.
--
It appears that all captures made on my OS X with radiotap headers have
inconsistent values for the Guard Interval between radiotap.mcs.gi &
wlan_radio.11n.short_gi

They are systematically inverted, cf pcap attached.

As a consequence, the data rate in radiotap & wlan_radio are always different
(radiotap.datarate & wlan_radio.data_rate)

Which one should I trust?

You are receiving this mail because:
  • You are watching all bug changes.