linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 15:29:16 +0200	[thread overview]
Message-ID: <1505482156.31630.39.camel@sipsolutions.net> (raw)
In-Reply-To: <ff73f237-71dd-5fde-9c9f-9bc8fce57e76@gmail.com> (sfid-20170915_145045_823652_4B4D42A4)

On Fri, 2017-09-15 at 07:50 -0500, Denis Kenzior wrote:

> > > E.g. if I CMD_CONNECT to AP1, then pre-authenticate to AP2 and
> > > issue a CMD_CONNECT to AP2?
> > 
> > That's not something you can do with full-MAC cards?
> 
> Err, why not?  Pre-Authentication runs over a 0x88c7 protocol.  So
> we should get these just like regular PAE frames.  But forget 
> pre-authentication, one can still force a roam between BSSes within
> the same ESS by specifying NL80211_ATTR_PREV_BSSID.  At least that's
> what the docs say ;)

Oh, you meant that kind of pre-authentication :-)

I thought you meant sending an 802.11 auth frame to the new AP before
breaking the connection to the old AP.

> > And even mac80211 doesn't really support pre-authentication (unless
> > you mean over-the-DS)

> 
> There's only one kind of preauthentication? Are you confusing this
> with FT?

No, see above.

> We use FT-over-Air just fine on mac80211 and on real hardware.  We 
> even have an autotest for this based on mac80211_hwsim.  FT-over-DS 
> should work as well.
> 
> Full macs don't support FT due to lack of 
> CMD_ASSOCIATE/CMD_AUTHENTICATE.  Can we fix that btw?

Well, with full MAC devices you should let the device decide on the
BSS?

johannes

  reply	other threads:[~2017-09-15 13:29 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 [this message]
2017-09-15 13:50                     ` Denis Kenzior
2017-09-15 14:20                       ` Johannes Berg
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=1505482156.31630.39.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).