From: Johannes Berg <johannes@sipsolutions.net>
To: Will Hawkins <hawkinsw@opentechinstitute.org>
Cc: Will Hawkins <hawkinsw@opentechinitiative.org>,
linux-wireless@vger.kernel.org
Subject: Re: Help tracing NL80211_CMD_AUTHENTICATE as event in IBSS mode
Date: Tue, 26 Jun 2012 19:03:30 +0200 [thread overview]
Message-ID: <1340730210.4484.11.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4FE9E6F0.2070909@opentechinstitute.org>
On Tue, 2012-06-26 at 12:44 -0400, Will Hawkins wrote:
> > Huh, now I'm confused, why would it need the authenticate frames for
> > IBSS? As far as I can tell, it looks at CMD_NEW_STA, which calls
> > nl80211_new_station_event(),
>
> This is what I understand as well.
>
> which in IBSS sends EVENT_IBSS_RSN_START to
> > the supplicant core -- that will trigger the 4-way-handshake. No? Hence
> > it doesn't need to register for auth frames, it never needs them, since
> > RSN uses open auth, if any is even used in IBSS at all.
>
> This is where I am still trying to figure out exactly how it works.
I believe that when the new station is added (NEW_STA event), it will
simply send out a 1/4 EAPOL frame. Since both do that, I guess it does
some kind of de-duplication? Whoever sends it first wins or something,
but I don't really know. Maybe we should take the discussion to the
hostap list at this point :-)
johannes
next prev parent reply other threads:[~2012-06-26 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 4:01 Help tracing NL80211_CMD_AUTHENTICATE as event in IBSS mode Will Hawkins
2012-06-26 6:53 ` Johannes Berg
2012-06-26 16:23 ` Will Hawkins
2012-06-26 16:41 ` Johannes Berg
2012-06-26 16:44 ` Will Hawkins
2012-06-26 17:03 ` Johannes Berg [this message]
2012-06-26 18:55 ` Antonio Quartulli
2012-06-26 18:56 ` Johannes Berg
2012-06-26 19:35 ` Antonio Quartulli
2012-06-26 19:36 ` Johannes Berg
2012-06-26 19:42 ` Nicolas Cavallari
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=1340730210.4484.11.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=hawkinsw@opentechinitiative.org \
--cc=hawkinsw@opentechinstitute.org \
--cc=linux-wireless@vger.kernel.org \
/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).