https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14454

            Bug ID: 14454
           Summary: Decoding of Tx Attenuation and Tx Attenuation in dB
                    fields in the Radiotap Header of the data link type
                    'IEEE802_11_RADIOTAP' is invalid
           Product: Wireshark
           Version: 2.4.1
          Hardware: x86
                OS: Windows 10
            Status: UNCONFIRMED
          Severity: Normal
          Priority: Low
         Component: Dissection engine (libwireshark)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: prasanthkumar.arise...@mathworks.in
  Target Milestone: ---

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
I have gone through the source code of Wireshark 2.4.1. In this i found that,
decoding of the 'Tx Attenuation' and 'Tx Attenuation dB' fields are of
ENC_BIG_ENDIAN. But, in the official link of radio tap header
http://www.radiotap.org/, it is mentioned that "Data is specified in little
endian byte-order, all data fields including the it_version, it_len and
it_present fields in the radiotap header are to be specified in little endian
byte-order. This wiki has adopted the Linux convention of using __le64, __le32
and __le16 for 64-, 32- and 16-bit little endian quantities."

So, decoding of these two fields must be in LITTLE_ENDIAN. It has to be fixed.

References :
https://elixir.bootlin.com/linux/v4.10.17/source/include/net/ieee80211_radiotap.h

https://ask.wireshark.org/question/1773/decoding-of-tx-attenuation-field-in-the-radiotap-header-of-the-data-link-type-ieee802_11_radiotap/

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to