Re: use of radiotap bit 14?

David Young wrote:
> On Thu, Jun 19, 2008 at 09:10:33PM +0200, Johannes Berg wrote:
>> Problem is, wireshark actually takes bit 14 to mean "FCS in header".
> 
> I'd forgotten about that, but I think that we still have some flexibility.

As per my mail, we can just take that out; OpenBSD defines it as "FCS in 
header", but doesn't appear to use it, and I don't know of any other 
system that uses it as "FCS in header".

Gerald, should we just remove the code that dissects 
IEEE80211_RADIOTAP_FCS from the 1.0.1 Wireshark release, in preparation 
for later releases interpreting presence bit 14 as RX flags?

The collision problem with 15 and 16 is worse - OpenBSD defines 15 as 
IEEE80211_RADIOTAP_HWQUEUE, and defines 16 as IEEE80211_RADIOTAP_RSSI, 
and several of their drivers use one or the other or both.  Wireshark 
currently doesn't dissect them; it should dissect them according to the 
standard.