From: Luciano Coelho <coelho@ti.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: Re: redesigning authentication/association flows
Date: Wed, 16 Nov 2011 13:57:16 +0200 [thread overview]
Message-ID: <1321444636.2408.112.camel@cumari> (raw)
In-Reply-To: <1321442014.4773.42.camel@jlt3.sipsolutions.net>
On Wed, 2011-11-16 at 12:13 +0100, Johannes Berg wrote:
> I've been growing unhappy with the way I designed authentication and
> association in cfg80211 and I'm ready to admit that the way it works now
> was a design mistake. Just see the tx_sync as an example, and if we
> explicitly do remain-on-channel for the authentication or association
> then we'll have to start doing GO NoA sync within r-o-c which will be a
> nightmare.
[...]
> Note that this gets rid of the stupid tx_sync, the attempt at doing this
> off-channel, and we never have to deal with tx_sync in remain-on-channel
> which would be really really strange.
>
> The only difference really is that today, if auth fails, we can stay
> connected. HOWEVER, wpa_supplicant isn't actually able to deal with
> that, gets confused and recovers with clear_state_mismatch().
>
>
> I think this will help all drivers, from at76c50x which is broken
> completely today, wl1251 which has a dummy join, wl12xx which has a work
> around with remain-on-channel but this doesn't work well with a GO (NoA)
> and of course iwlwifi (which has tx_sync for this) and iwlegacy which
> has a bunch of RXON ping-pong things going on.
As discussed on the phone, I think this should be okay with wl12xx. We
will have to study it a bit further to be sure, but my first impression
is that it's should be fine.
One small correction from my mistake, wl1251 doesn't have a dummy join,
it's the old wl12xx which did (with older firmwares that didn't support
roc/croc). Sorry, I got confused.
--
Cheers,
Luca.
prev parent reply other threads:[~2011-11-16 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 11:13 redesigning authentication/association flows Johannes Berg
2011-11-16 11:57 ` Luciano Coelho [this message]
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=1321444636.2408.112.camel@cumari \
--to=coelho@ti.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--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