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: Mon, 13 Aug 2007 10:51:44 +0200 [thread overview]
Message-ID: <1186995104.27916.56.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240708120358rb22a2f9me1a1020e669406e7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Sun, 2007-08-12 at 13:58 +0300, Tomas Winkler wrote:
> Isn't the removal of management interface a bit premature? I didn't
> see any proposal how to move management packets to the application
> level? If not I would prefer eapol packets be treated on management
> path. No data should be received on data interface till security
> negotiation is done.
Have you read the patch or are you just ranting? I'm guessing the
latter? The patch didn't remove the management interface at all.
Besides, what point is there in not allowing EAPOL packets through? They
are fundamentally data packets so they belong onto the AP mode ethernet
framed device, and they won't be interpreted by any other application.
You'll have to come up with better reasons than "I prefer" blabla.
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-13 9:00 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 [this message]
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
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=1186995104.27916.56.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