Comment # 12
on bug 10139
from Guy Harris
At least in
http://www.loplof.de/kram/airopeek.pcap.gz
if I change the PEEKREMOTE dissector to call the wlan_withfcs dissector rather
than the wlan_datapad_withfcs dissector, packets 3 and 5, for example, dissects
correctly *and* shows a correct FCS (rather than two of the bytes at the end
being ignored and two of them treated as Atheros padding). No other frames
dissect differently.
So, with a *current* version of the 802.11 dissector, are there any QoS frames
with the extra bytes? (Were the extra bytes the result of the 802.11
dissector, back in 2007, not handling QoS frames correctly, with the extra
bytes perhaps being QoS header bytes, and treating them as Atheros padding kept
the dissector from being confused about them?)
You are receiving this mail because:
- You are watching all bug changes.