Re: Plans for an online meeting regarding Radiotap

Guy Harris <guy-FrUbXkNCsVf2fBVCVOL8/[email protected]>
Newsgroups org.netbsd.radiotap
Message-ID <[email protected]>
On Aug 24, 2009, at 11:55 AM, Guy Harris wrote:

>> Wireshark:
>> Field 14: RX flags, with option to decode FCS instead
>> Fields 15...17 skipped
>
> No:
>
> Fields 15...17: not implemented, so if any of them are present, no  
> later fields are dissected
>
> Also:
>
> Tcpdump top-of-tree at tcpdump.org:
>
> Fields 14...17: not implemented, so if any of them are present, no  
> later fields are dissected
> Field 18: extended channel

Although field 18 is, I think, used only by FreeBSD, and it doesn't  
use fields 15-17, so those won't cause a problem for field 18.

>> My current proposal for the future standard field ordering beyond  
>> field 14:
>>
>> Field 14: RX flags (as defined by the standard)
>> Field 15: TX flags (as used by Linux, NetBSD and aircrack-ng)
>> Field 16: RTS retry count (as used by Linux and NetBSD)
>> Field 17: Data retry count (as used by Linux and NetBSD)
>> Field 18: Extended channel (as used by FreeBSD and Wireshark)
>
> ...and top-of-tree tcpdump.org tcpdump (taken from FreeBSD's tcpdump).

Sorry, that was a bit unclear - "...and top-of-tree tcpdump.org  
tcpdump (taken from FreeBSD's tcpdump)" applies to field 18, not to  
the other fields.

We should probably add support for field 14 (as defined by the  
standard) to tcpdump.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.