From: Johannes Berg <johannes@sipsolutions.net>
To: Denis Kenzior <denkenz@gmail.com>,
Arend van Spriel <arend@broadcom.com>, Jouni Malinen <j@w1.fi>
Cc: Avraham Stern <avraham.stern@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ROAM/CONNECT event with PORT_AUTHORIZED
Date: Fri, 15 Sep 2017 16:20:08 +0200 [thread overview]
Message-ID: <1505485208.31630.42.camel@sipsolutions.net> (raw)
In-Reply-To: <9b466254-e9c1-c5e4-c3fd-b881c4c583e9@gmail.com> (sfid-20170915_155043_885561_8E371F43)
On Fri, 2017-09-15 at 08:50 -0500, Denis Kenzior wrote:
> > I thought you meant sending an 802.11 auth frame to the new AP
> > before breaking the connection to the old AP.
> >
>
> I mean 802.11-2012 Section 11.5.9.2 type preauthentication.
Yeha, OK.
> And AFAIK the kernel generates a disconnected event as soon as we
> send a CMD_AUTHENTICATE, so not sure how you envision 'your'
> preauthentication working...
That's what I was trying to say - it doesn't. A few years ago we tried
to support that but it's not really possible to do well.
> However, you're not answering my question...
Which was?
> > Well, with full MAC devices you should let the device decide on the
> > BSS?
> >
>
> Why? So we can deal with the various ways a vendor firmware can
> screw up? Besides, you have an asymmetry in the kernel API.
:)
> One can use regular roaming on a full mac but not FT.
We had intended to have NL80211_CMD_ROAM to make that decision once,
but never really used it for that... I think it could be implemented
but I don't really know how well drivers were to support it.
johannes
next prev parent reply other threads:[~2017-09-15 14:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 8:39 ROAM/CONNECT event with PORT_AUTHORIZED Johannes Berg
2017-09-14 11:21 ` Arend van Spriel
2017-09-14 11:44 ` Johannes Berg
2017-09-14 18:37 ` Denis Kenzior
2017-09-14 19:17 ` Johannes Berg
2017-09-14 19:34 ` Denis Kenzior
2017-09-14 19:38 ` Ben Greear
2017-09-14 20:05 ` Denis Kenzior
2017-09-14 20:08 ` Ben Greear
2017-09-14 20:26 ` Denis Kenzior
2017-09-14 20:29 ` Ben Greear
2017-09-14 20:35 ` Denis Kenzior
2017-09-14 20:47 ` Ben Greear
2017-09-14 21:35 ` Denis Kenzior
2017-09-14 22:15 ` Ben Greear
2017-09-14 22:42 ` Denis Kenzior
2017-09-14 22:57 ` Ben Greear
2017-09-15 7:23 ` Johannes Berg
2017-09-15 7:20 ` Johannes Berg
2017-09-14 19:39 ` Johannes Berg
2017-09-14 18:27 ` Denis Kenzior
2017-09-14 18:36 ` Johannes Berg
2017-09-14 19:08 ` Denis Kenzior
2017-09-14 19:22 ` Johannes Berg
2017-09-14 19:37 ` Denis Kenzior
2017-09-14 19:41 ` Johannes Berg
2017-09-14 19:42 ` Johannes Berg
2017-09-14 19:54 ` Denis Kenzior
2017-09-15 7:19 ` Johannes Berg
2017-09-15 12:50 ` Denis Kenzior
2017-09-15 13:29 ` Johannes Berg
2017-09-15 13:50 ` Denis Kenzior
2017-09-15 14:20 ` Johannes Berg [this message]
2017-09-15 14:27 ` Denis Kenzior
2017-09-15 14:52 ` 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=1505485208.31630.42.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=avraham.stern@intel.com \
--cc=denkenz@gmail.com \
--cc=j@w1.fi \
--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).