Hi,
Using tshark -2 -r Dump2.pcapng -T fields -e wlan_radio.data_rateon a OTA dump ( https://remy.grunblatt.org/Dump2.pcapng ), I get values such as "6.5,6.5" or "526.5,526.5".
From the documentation, the values are supposed to be Floating point (single-precision). Is there a problem with the pcap? Or is that a problem with tshark?
There are two reports of the rate as the field appears twice in the wlan_radio block, once under the wlan_radio.11ac.user (User 1:) block and once under the main block. I'm not familiar enough with WLAN captures to say if this is a dissector error or not, but I would think that there should either be one entry, or there should be different field names. Please raise an issue on the Wireshark Bugzilla for this.
The "single-precision" part of the definition is that the field is an IEEE 754 single precision float with a range of ± 2-126 to (2-2-23)×2127
A fix has been checked in. In a VHT frame, there will now be exactly one data rate field instance per user.
And note that the documentation to which you refer does not state that there will be only one instance of the field in question, so the fact that it says the values are floating-point does not mean that there will be only one value, it just means that the values - possibly more than one - will be floating-point values.
Asked: 2019-07-19 11:53:15 +0000
Seen: 265 times
Last updated: Jul 19 '19
