From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Tomas Winkler <tomasw@gmail.com>,
mohamed salim abbas <mabbaswireless@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Michael Wu <flamingice@sourmilk.net>
Subject: Re: A-MSDU deaggregation support
Date: Thu, 27 Sep 2007 18:39:56 -0700 [thread overview]
Message-ID: <20070928013956.GK27241@jm.kir.nu> (raw)
In-Reply-To: <1190792394.18521.354.camel@johannes.berg>
On Wed, Sep 26, 2007 at 09:39:54AM +0200, Johannes Berg wrote:
> So any STA can actually send EAPOL frames with an arbitrary destination
> MAC address except our own into our 802.3 interface. Hence, it looks
> like the first case above is only for having eapol on mgmt iface.
EAPOL ethertype is not supposed to be bridged, so it would be perfectly
fine dropping these wherever it is most convenient to do.
> The only problem I see with not doing this is that hostapd will have to
> listen for EAPOL frames on all VLAN interfaces but I suppose that is
> doable.
That's fine. This should be doable with just one packet socket that is
not bound to any interface or alternatively with multiple sockets (one
per interface). I wouldn't be too concerned about the extra cost here as
long as the other EAPOL related silliness (e.g., the difference in
encryption of re-keying packets in 802.1X with dynamic WEP vs. WPA).
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-09-28 1:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 16:15 A-MSDU deaggregation support Johannes Berg
2007-09-10 11:41 ` Tomas Winkler
2007-09-10 11:49 ` Johannes Berg
2007-09-25 19:19 ` Johannes Berg
2007-09-25 23:24 ` Tomas Winkler
2007-09-26 7:39 ` Johannes Berg
2007-09-26 11:46 ` Tomas Winkler
2007-09-26 12:16 ` Johannes Berg
2007-09-26 12:32 ` Tomas Winkler
2007-09-26 12:37 ` Johannes Berg
2007-09-28 1:39 ` Jouni Malinen [this message]
2007-09-28 8:34 ` 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=20070928013956.GK27241@jm.kir.nu \
--to=j@w1.fi \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mabbaswireless@gmail.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