From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas d'Otreppe <tdotreppe@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Monitor mode 'cook' flag meaning
Date: Tue, 21 Feb 2017 00:26:51 +0100 [thread overview]
Message-ID: <1487633211.484.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CALs6+XLDZLmc6JWMPun4sT+W_M4Cqh47LcK+HjiuZ8gKFLkbTA@mail.gmail.com> (sfid-20170221_002306_313869_E4D6D4DA)
On Mon, 2017-02-20 at 16:22 -0700, Thomas d'Otreppe wrote:
> I've been looking through the different flags for monitor mode in iw.
> Most of them are rather obvious (and well explained) but what is
> exactly 'cooked mode'?
>
> I looked up in Google and in the linux-wireless wiki (nothing in
> there) and I only found explanations in 2 patches (most likely still
> in the source code) which are still vague:
> - A monitor interface in "cooked" mode will see all frames that
> mac80211 has not used internally
> - report frames after processing. Overrides all other flags.
>
> Thinking about what the first one says, it doesn't seem any different
> than just fcsfail.
No, that's the wrong idea. "cook" means that e.g. auth frames that
mac80211 didn't actually look at will be sent there.
Anyway, ignore cooked mode. It's only for ancient hostapd versions.
> I don't even see when control or otherbss should be needed since
> 'none' is already providing them.
Those are hw-dependent.
johannes
next prev parent reply other threads:[~2017-02-20 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 23:22 Monitor mode 'cook' flag meaning Thomas d'Otreppe
2017-02-20 23:26 ` Johannes Berg [this message]
2017-02-21 1:46 ` Thomas d'Otreppe
2017-02-21 8:37 ` 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=1487633211.484.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tdotreppe@gmail.com \
/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).