https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7000
--- Comment #2 from Jelmer de Hen <jelmerdehen@xxxxxxxxxxx> 2012-03-26 14:24:17 PDT ---
Hi Guy Harris,
Your assumption about it being inside the present flags of the radiotap header
are right, typo on my side.
What I meant is that the TX attenuation is on the same bit as the dB TX
attenuation.
I suspect this will be properly handled internally but when you look in the gui
you can notice that the bits are both on the DB TX attenuation bit.
How it is:
.... .... .... .... .... ..X. .... .... DB TX Attenuation
.... .... .... .... .... ..X. .... .... DBM TX Attenuation
How it probably should be:
.... .... .... .... .... ..X. .... .... DB TX Attenuation
.... .... .... .... .... .X.. .... .... DBM TX Attenuation
I can include a screenshot if you like
Also in tshark it dumps it in this format:
.... .... .... .... .... .... 0... .... = Lock Quality: False
.... .... .... .... .... ...0 .... .... = TX Attenuation: False
.... .... .... .... .... ..0. .... .... = DB TX Attenuation: False
.... .... .... .... .... ..0. .... .... = DBM TX Attenuation: False
.... .... .... .... .... 1... .... .... = Antenna: True
While for example this googled page:
http://forums.fanfaresoftware.com/fnfr/attachments/fnfr/iTestGeneral/9008/1/response.txt
>From what I know that dump is displaying the DBM TX Attenuation bit on the
right spot.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
