linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
	Jouni Malinen <j@w1.fi>, Eric Blau <eblau@eblau.com>
Cc: hostap@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Kernel oops / WiFi connection failure with wpa_supplicant 2.7
Date: Tue, 15 Jan 2019 09:55:06 -0600	[thread overview]
Message-ID: <3010fb21-f8c4-640d-782c-328ca6c21b2a@gmail.com> (raw)
In-Reply-To: <d5599cf9-5fb4-a68d-dfd9-0d10a6758ae2@broadcom.com>

Hi Arend,

>>>
>>>> - Is RTNL LINK_MODE / OPER_STATE status being (supposed to be?) 
>>>> affected by the driver during a roam?  E.g. if we're in a 802.1X 
>>>> network with userspace authentication, and driver roamed requiring a 
>>>> new 802.1X auth, then in theory the RTNL mode needs to be brought 
>>>> back out of UP state...
>>>
>>> So do you expect the driver/cfg80211 to take care of that or the 
>>> supplicant? I assumed wpa_supplicant would be doing that.
>>>
>>
>> With regular roaming where we trigger a Deassociate/Deathenticate 
>> (either explicitly or implicitly) first, the interface goes into 
>> dormant mode by virtue of the carrier going down.
>>
>> With this it isn't really clear whether the same is happening and who 
>> (kernel/userspace) should be doing what.  I would actually assume the 
>> kernel is/should be turning carrier off for the duration of the roam 
>> operation?
> 
> On what layer do we know 802.1X re-auth is required?
> 

Not sure what you mean by 'layer'?  If re-auth is required, then only 
the supplicant has the proper info and it will handle this via EAPoL frames.

But that is besides the point.  Regardless of whether a roam needs 
re-auth or not, network interface dormant notification is needed.  For 
example: userspace DHCP clients need to know when to renew the address. 
And yes, there are weird networks out there that expect you to 
re-negotiate your DHCP address on a roam.  Such clients are not 
integrated in any way with a supplicant and rely on rtnl.

Regards,
-Denis

      parent reply	other threads:[~2019-01-15 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADU241PtPeiTQWHwb=uF6Ohuua_asOwCarCAKVC8jdVVNAsByA@mail.gmail.com>
     [not found] ` <20190103154921.GA25015@w1.fi>
2019-01-05 19:44   ` Kernel oops / WiFi connection failure with wpa_supplicant 2.7 Arend Van Spriel
2019-01-08 17:44     ` Denis Kenzior
2019-01-14 20:12       ` Arend Van Spriel
2019-01-14 21:18         ` Denis Kenzior
2019-01-14 23:04           ` Arend Van Spriel
2019-01-15 13:00             ` Johannes Berg
2019-01-15 15:55             ` Denis Kenzior [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=3010fb21-f8c4-640d-782c-328ca6c21b2a@gmail.com \
    --to=denkenz@gmail.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=eblau@eblau.com \
    --cc=hostap@lists.infradead.org \
    --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).