From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "mohamed salim abbas" <mabbaswireless@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Michael Wu" <flamingice@sourmilk.net>, "Jouni Malinen" <j@w1.fi>
Subject: Re: A-MSDU deaggregation support
Date: Wed, 26 Sep 2007 01:24:22 +0200 [thread overview]
Message-ID: <1ba2fa240709251624ycb516c4t90bcb6846800b18@mail.gmail.com> (raw)
In-Reply-To: <1190747966.18521.320.camel@johannes.berg>
On 9/25/07, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Mon, 2007-09-10 at 14:41 +0300, Tomas Winkler wrote:
>
> > There is actually different problem with the A-MSDU deaggregation and
> > this is EPOL filtering. One of the packets might belong to EAPOL
> > handshake
>
> Why do we filter those anyway? What's wrong with having them show up on
> the regular 802.3 framed interface all the time? Isn't that how 802.1X
> was basically designed?
>
EAPOL frames should not be filtered out. Everything else should be filtered out
except EAPOL frames till the port is open.
The problem is the order of the handlers. First you need to
deaggregated the frame then filtered out non EAPLOL frames if the port
is not open.
Tomas
> johannes
>
>
next prev parent reply other threads:[~2007-09-25 23:24 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 [this message]
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
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=1ba2fa240709251624ycb516c4t90bcb6846800b18@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mabbaswireless@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