From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Dennis New <dennisn@dennisn.mooo.com>,
linux-wireless@vger.kernel.org
Subject: Re: wlan0 keeps deauthenticating DEAUTH_LEAVING about every minute
Date: Wed, 29 Mar 2017 10:50:13 +0200 [thread overview]
Message-ID: <1490777413.7948.14.camel@sipsolutions.net> (raw)
In-Reply-To: <260a3f4a-1ee1-62ec-e3db-294510e71a4e@broadcom.com> (sfid-20170329_102018_969097_22371F10)
> > This code was designed for regulatory changes, but the WARN_ON()
> > indicates that we got connected on a channel that we think isn't
> > actually usable. We quite possibly should reject that connection
> > there, but it seems to me it should've been rejected elsewhere
> > already...?
>
> But this is prior to connection, right? This warning happens upon
> authenticate.
Yeah the warning happens in authentication.
> So in nl80211_authenticate() we do:
>
> chan = nl80211_get_valid_chan(&rdev->wiphy,
> info->attrs[NL80211_ATTR_WIPHY_FREQ]);
>
> and in cfg80211_mlme_auth():
>
> req.bss = cfg80211_get_bss(&rdev->wiphy, chan, bssid, ssid, ssid_len,
> IEEE80211_BSS_TYPE_ESS,
> IEEE80211_PRIVACY_ANY);
That might not be what's going on - the OP said he was getting this
with iw, which doesn't go through nl80211_authenticate() but
nl80211_connect().
> After that the chain is:
>
> ieee80211_mgd_auth() ->
> ieee80211_prep_connection() ->
> ieee80211_prep_channel() ->
> ieee80211_determine_chantype()
And somehow that determines that even a 20MHz no-HT channel isn't
valid.
johannes
next prev parent reply other threads:[~2017-03-29 8:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 1:32 wlan0 keeps deauthenticating DEAUTH_LEAVING about every minute Dennis New
2017-03-26 16:00 ` Larry Finger
2017-03-26 17:43 ` Dennis New
2017-03-26 18:47 ` Arend Van Spriel
2017-03-26 18:51 ` Dennis New
2017-03-26 19:00 ` Arend Van Spriel
2017-03-29 7:34 ` Johannes Berg
2017-03-29 7:43 ` Arend Van Spriel
2017-03-29 7:46 ` Johannes Berg
2017-03-29 8:20 ` Arend Van Spriel
2017-03-29 8:50 ` Johannes Berg [this message]
2017-03-29 10:28 ` Dennis New
2017-03-29 11:49 ` Johannes Berg
2017-03-29 18:58 ` Arend Van Spriel
2017-03-30 8:06 ` Johannes Berg
2017-03-29 19:36 ` Dennis New
2017-03-29 20:15 ` Larry Finger
2017-03-29 20:21 ` Arend Van Spriel
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=1490777413.7948.14.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=dennisn@dennisn.mooo.com \
--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).