From: Johannes Berg <johannes@sipsolutions.net>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: question regarding cfg80211 monitor modes
Date: Thu, 03 Dec 2009 11:54:42 +0100 [thread overview]
Message-ID: <1259837682.12843.10.camel@johannes.local> (raw)
In-Reply-To: <200912031148.46934.holgerschurig@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
On Thu, 2009-12-03 at 11:48 +0100, Holger Schurig wrote:
> "iw wlan0 set type monitor" allows the following flags:
>
> none: no special flags
> fcsfail: show frames with FCS errors
> control: show control frames
> otherbss: show frames from other BSSes
> cook: use cooked mode
>
> However, I don't know how to map them to the Libertas' firmware
> flags, which has
>
> Libertas (bits can be ored)
> Data frames 0x01
> Mgmt frames but beacons 0x02
> Beacons 0x04
>
>
> So I guess that the following could be a translation table:
>
> none 0x00
> fcsfail -ENOTSUPP
> control 0x02 | 0x04
>
> But what should "otherbss" and "cook" be?
"cook" and "none" only make sense while operating in a different mode at
the same time. For "cook" you get frames that the kernel hasn't
consumed. For "none" you don't influence the filters due to the monitor.
I suspect you don't support concurrent operation, so neither of those
makes sense.
fcsfail/plcpfail are probably not supported.
From what you say, "control" isn't supported either, since you were
talking about management frames, not control frames. "otherbss" is for
showing frames with a different BSSID, and in libertas monitor mode
probably always enabled.
I'd say don't bother with the flags at all.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-12-03 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 10:48 question regarding cfg80211 monitor modes Holger Schurig
2009-12-03 10:54 ` Johannes Berg [this message]
2009-12-03 11:00 ` Holger Schurig
2009-12-03 14:46 ` Luis R. Rodriguez
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=1259837682.12843.10.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=holgerschurig@gmail.com \
--cc=linux-wireless@vger.kernel.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