radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Cc: Andy Green <andy-/Zus8d0mwwtBDgjK7y7TUQ@public.gmane.org>
Subject: parser with vendor extensions
Date: Thu, 26 Nov 2009 11:29:33 +0100	[thread overview]
Message-ID: <1259231373.32372.55.camel@johannes.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

Hi,

Andy Green had graciously allowed us to use his radiotap parser he wrote
for the Linux kernel under BSD license for hostapd.

I've lifted that parser into a separate project at
http://git.sipsolutions.net/radiotap.git/ (both git clone and gitweb)
and added namespace/vendor extension support.

It's easy to embed into other projects and I'm hoping to eventually make
wireshark use it, its home-grown parser is really reaching its limits
and doesn't even parse current standard radiotap properly (it doesn't
handle bitmap extension bits properly afaict).

It also contains test cases for radiotap headers that I think are valid
along with how they should be parsed. More test cases, and especially
review of the existing ones would be very welcome.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2009-11-26 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 10:29 Johannes Berg [this message]
     [not found] ` <1259231373.32372.55.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-11-26 18:42   ` parser with vendor extensions Johannes Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1259231373.32372.55.camel@johannes.local \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=andy-/Zus8d0mwwtBDgjK7y7TUQ@public.gmane.org \
    --cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).