radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Roberto Riggio <roberto.riggio-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
Cc: Bill Stafford <bill.stafford-BUHhN+a2lJ4@public.gmane.org>,
	radiotap-qavaossjCcEdnm+yROfE0A@public.gmane.org
Subject: Re: Sample parser for radiotap header
Date: Wed, 02 Mar 2011 09:21:03 +0100	[thread overview]
Message-ID: <1299054063.4076.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4D67F6A1.6060301-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>

On Fri, 2011-02-25 at 19:36 +0100, Roberto Riggio wrote:

> Is this supposed to know about extended present bitmask? I'm creating
> a packet with four chained present bitmask in order to specify a MRR
> chain.
> 
> The problem is that when I'm trying to parse the header with the lib
> only the first "block" is parsed. In fact when I use the function:
> 
> ieee80211_radiotap_iterator_next
> 
> I get ENOENT as return code when the bit 31 is reached. Same result
> i I try to pass this packet to the linux kernel where the iterator
> implementation is the same.

You must be doing something wrong then, it is definitely parsing such
radiotap headers, hopefully correctly. There are examples in the check/
directory for it, e.g. 00.bin:
00000000  00 00 20 00 01 00 00 a0  01 00 00 00 00 00 00 00 
00000010  11 22 33 44 55 66 77 88  aa bb cc dd ee ff 00 11

is a radiotap header with two TSFT fields. I think you most likely
forgot to reset the namespace.

johannes

  parent reply	other threads:[~2011-03-02  8:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23  9:05 Sample parser for radiotap header Roberto Riggio
     [not found] ` <4D64CDBF.8010100-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
2011-02-23  9:24   ` Johannes Berg
2011-02-24  6:16   ` Bill Stafford
     [not found]     ` <408dc500-c062-ede0-c040-d21a120a386c-BUHhN+a2lJ4@public.gmane.org>
2011-02-25 18:36       ` Roberto Riggio
     [not found]         ` <4D67F6A1.6060301-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
2011-03-02  8:21           ` Johannes Berg [this message]
     [not found]             ` <1299054063.4076.2.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2011-03-02  8:42               ` Roberto Riggio
     [not found]                 ` <4D6E0306.1020307-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
2011-03-02  8:45                   ` Johannes Berg
     [not found]                     ` <4D6E050E.3030807@create-net.org>
     [not found]                       ` <4D6E050E.3030807-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
2011-03-02  8:53                         ` Johannes Berg
     [not found]                           ` <1299056027.4076.7.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2011-03-02  9:01                             ` Roberto Riggio
     [not found]                               ` <4D6E0758.3050809-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
2011-03-02  9:03                                 ` 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=1299054063.4076.2.camel@jlt3.sipsolutions.net \
    --to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
    --cc=bill.stafford-BUHhN+a2lJ4@public.gmane.org \
    --cc=radiotap-qavaossjCcEdnm+yROfE0A@public.gmane.org \
    --cc=roberto.riggio-2TmCWn7/4sHOQU1ULcgDhA@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).