From: Denis Kenzior <denkenz@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Arend van Spriel <arend.vanspriel@broadcom.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: Thu, 14 Sep 2017 13:37:55 -0500 [thread overview]
Message-ID: <e418234f-00a0-dd44-7352-d279f49f83e5@gmail.com> (raw)
In-Reply-To: <1505389462.31630.6.camel@sipsolutions.net>
Hi Johannes,
On 09/14/2017 06:44 AM, Johannes Berg wrote:
> On Thu, 2017-09-14 at 13:21 +0200, Arend van Spriel wrote:
>
>> Yep. Toggling the OPER_STATE seems to go against what roaming is
>> about.
>
> Agree.
The question is whether all APs are actually sane after a roam. E.g.
can the STA assume that the same IP address, DHCP lease, etc is still
valid? I heard from various people that this might not be the case, but
we haven't had a chance to verify those claims...
>
>> Come to think of it, is it a good idea to tightly couple
>> PORT_AUTHORIZED to OPER_STATE. Aren't these separate concepts in
>> different layers of the network stack.
>
> Well, I think that coupling would make the most sense, since once you
> have oper state UP you'll try to get IPv6 etc., no? And before being
> authorized there's no point.
>
I think it does make sense to tie one into the other. However, do we
have a race condition here? E.g. AUTHORIZED is sent on one socket, then
OPER_STATE is signaled on rtnl. Which one do applications rely on?
> Note that we *can't* do this right now, otherwise we can't transfer the
> EAPOL frames; but once we do that over nl80211 we'd be able to.
>
>> In earlier discussions the proposal for a separate event was made by
>> Jithu (colleague). In brcmfmac it would become a bit less
>> complicated with a separate event so it has my vote as well. So the
>> AUTHORIZED event will have no attributes, right? So if the event
>> occurs it is AUTHORIZED.
>
> I think so, yes. I pondered having the attribute in there so you could
> explicitly have a "not authorized" event, but do we really need that?
> If you get disconnected that's pretty much implied, so ... I don't
> think we need it.
>
>
>>> (*) is anyone working on that? I'll throw it on my list if not.
>
> ["that" being EAPOL-over-nl80211]
>
>> The last I saw on this was Denis Kenzior volunteering for it, but
>> that was about it.
>
> Oh, thanks for the reminder, I'd forgotten entirely...
> Denis?
*wakes up*
Ah I now seem to remember that I volunteered to look into this before my
sabbatical :) I think this was in early June? I'm certainly still
interested in doing so. Let me dust off that portion of my brain and
come up with a proposal. Unless you already have a clear idea of how
things should work?
Regards,
-Denis
next prev parent reply other threads:[~2017-09-14 18:37 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 [this message]
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
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=e418234f-00a0-dd44-7352-d279f49f83e5@gmail.com \
--to=denkenz@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=avraham.stern@intel.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;
as well as URLs for NNTP newsgroup(s).