From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Jiri Benc <jbenc@suse.cz>,
linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH] hostapd: use eapol frames from ethernet device
Date: Wed, 15 Aug 2007 12:58:56 +0200 [thread overview]
Message-ID: <1187175536.3998.21.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240708141546g4de44ff1v94db00213a3187aa@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Wed, 2007-08-15 at 01:46 +0300, Tomas Winkler wrote:
> Can you enlighten me and tell me why the monitor interface is
> preferable over management interface? I've probably got busy and
> missed the whole conversation.
Oh, I can name a number of reasons :)
* magic needed to conjure it
* munged prism2 header that nothing but hostapd/wpa_supplicant
understands
* special cases all over the code to stuff frames there
> I'm not so familiar with monitor interface but isn't it to be
> sniffing interface - everything goes up including data raw packets.
Well, in a way you're right. But please review the recent filter flags
patches I posted. And I'm using BPF to avoid seeing data frames other
than those I need.
> What if management frames needs decryption? I think this is 802.11w
> specs that defines that.
I thought radiotap injection could handle that, but it turns out that I
need to think again, especially about EAPOL frames. I'll address these
things in a reply to Jouni's mail, but that'll take a bit longer than
just going through and replying.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-08-15 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 23:48 [PATCH] mac80211: remove special casing of EAPOL on mgmt interface Johannes Berg
2007-08-10 23:53 ` [PATCH] hostapd: use eapol frames from ethernet device Johannes Berg
2007-08-12 10:58 ` Tomas Winkler
2007-08-13 8:51 ` Johannes Berg
2007-08-13 10:46 ` Tomas Winkler
2007-08-13 11:02 ` Johannes Berg
2007-08-14 22:46 ` Tomas Winkler
2007-08-15 10:58 ` Johannes Berg [this message]
2007-08-15 4:16 ` Jouni Malinen
2007-08-20 11:57 ` 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=1187175536.3998.21.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=jbenc@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@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