Bug#833507: [pkg-wpa-devel] Bug#833507: wpasupplicant: Unable to connect WLAN (wlan0: CTRL-EVENT-SCAN-FAILED ret=-22)

[Eduard Bloch]

clone 833507 -1
retitle -1 network-manager drives broadcom driver into confused state
reassign -1 network-manager
thanks

On Sat, 3 Sep 2016 22:00:48 +0200 "Eduard Bloch"  
wrote:
> On Tue, 9 Aug 2016 17:27:58 +1000 Barry Kitson  wrote:
> > Just confirming version 2.5-2+v2.4-1 currently in the debian repository
> > works for me.
> 
> Sorry, for me that does NOT work, at least not fully. I have a Lenovo
> laptop with a similar Broadcom chip, i.e. only non-free driver supports
> it. Still getting lots of:
> 
> wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
> 
> and nothing works, apart from getting the initial AP list.
> 
> However, this happens only with network-manager. Just for testing, I
> configured a wpa_supplicant.conf manually and run wpa_supplicant
> manually with that file, and also run dhclient manually. And I got
> a working network connection!
> 
> So IMHO this might be somehow connected to network-manager.

So I tried more of that for a while and it seems to be reproducible.

a) I stop wpasupplicant service and run wpa_supplicant manually. I see chaotic
disconnects/reconects (see below, slightly anonymized) which seem to be
triggered by network-manager.

b) I stop network-manager service and run wpa_supplicant manually. It seems to
associate just fine. I run dhclient manually, it gets the IP, and the link is
OK for days. Even after suspend/resume cycles, it reassociates and/or switches 
the
AP as needed and continues without any glitches (see the last log below). 

So for me there seems to be a trend... whatever NM is doing to wpa_supplicant
or the driver, it's no good. And it has been working fine for a couple of years
before one of the recent upgrades broke it.

Successfully initialized wpa_supplicant
rfkill: Cannot open RFKILL control device
wlan0: Trying to associate with 00:1f:3f:15:f4:2d (SSID='ANON_nomap' freq=2472 
MHz)
wlan0: Associated with 00:1f:3f:15:f4:2d
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1f:3f:15:f4:2d reason=0
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="ANON_nomap" auth_failures=1 
duration=10 reason=WRONG_KEY
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: Trying to associate with 00:24:fe:04:fc:bb (SSID='ANON2_nomap' freq=2452 
MHz)
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:24:fe:04:fc:bb reason=0
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: Associated with 00:24:fe:04:fc:bb
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:24:fe:04:fc:bb reason=0
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="ANON2_nomap" auth_failures=1 
duration=10 reason=WRONG_KEY
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="ANON_nomap"
wlan0: Trying to associate with 00:1f:3f:15:f4:2d (SSID='ANON_nomap' freq=2472 
MHz)
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1f:3f:15:f4:2d reason=0
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: Associated with 00:1f:3f:15:f4:2d
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1f:3f:15:f4:2d reason=0
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="ANON_nomap" auth_failures=2 
duration=23 reason=WRONG_KEY
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="ANON_nomap" auth_failures=3 
duration=46 reason=CONN_FAILED
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: CTRL-EVENT-SSID-REENABLED id=1 ssid="ANON2_nomap"
wlan0: Trying to associate with 00:24:fe:04:fc:bb (SSID='ANON2_nomap' freq=2452 
MHz)
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:24:fe:04:fc:bb reason=0
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: Associated with 00:24:fe:04:fc:bb
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:24:fe:04:fc:bb reason=0
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="ANON2_nomap" auth_failures=2 
duration=37 reason=WRONG_KEY
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="ANON2_nomap" auth_failures=3 
duration=55 reason=CONN_FAILED
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT 

Bug#833507: [pkg-wpa-devel] Bug#833507: wpasupplicant: Unable to connect WLAN (wlan0: CTRL-EVENT-SCAN-FAILED ret=-22)

[Eduard Bloch]

On Tue, 9 Aug 2016 17:27:58 +1000 Barry Kitson  wrote:
> Just confirming version 2.5-2+v2.4-1 currently in the debian repository
> works for me.

Sorry, for me that does NOT work, at least not fully. I have a Lenovo
laptop with a similar Broadcom chip, i.e. only non-free driver supports
it. Still getting lots of:

wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1

and nothing works, apart from getting the initial AP list.

However, this happens only with network-manager. Just for testing, I
configured a wpa_supplicant.conf manually and run wpa_supplicant
manually with that file, and also run dhclient manually. And I got
a working network connection!

So IMHO this might be somehow connected to network-manager.

Regards,
Eduard.

Bug#833507: [pkg-wpa-devel] Bug#833507: wpasupplicant: Unable to connect WLAN (wlan0: CTRL-EVENT-SCAN-FAILED ret=-22)

[Barry Kitson]

Just confirming version 2.5-2+v2.4-1 currently in the debian repository
works for me.

Thanks for the fix, at least for now.

Bug#833507: [pkg-wpa-devel] Bug#833507: wpasupplicant: Unable to connect WLAN (wlan0: CTRL-EVENT-SCAN-FAILED ret=-22)

[Andrew Shadura]

On 05/08/16 10:51, Support wrote:
> after update to version 2.5-1 or 2.5-2 i am not able to connect to our WLAN 
> anymore.
> Downgrading to version 2.3-2.4 solves the problem. Here the syslog entries 
> (complete
> block of consecutive lines from syslog - nothing deleted, only a bit 
> anonymized):

Based on a private conversation with Robert I decided to upload wpa v2.4
as 2.5-2+v2.4+1 as that doesn't seem to have this bug, and it's been
used and tested by Ubuntu for quite some time.

-- 
Cheers,
  Andrew



signature.asc
Description: OpenPGP digital signature