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

2017-12-10 Thread Andrew Shadura 
On 9 December 2017 at 17:25, YOSHINO Yoshihito  wrote:
> Package: wpasupplicant
> Version: 2:2.6-13
> Followup-For: Bug #833507
>
> Dear Maintainer,
>
> I use /etc/network/interfaces to configure networking, not network-manager.
> Upgrading wpasupplicant to >= 2:2.6 my machine (MacBook Air with broadcom-sta
> wl module) fails to connect to a wi-fi network, with a lot of syslog messages
> of "CTRL-EVENT-SCAN-FAILED ret=-22".
> Downgrading the package to 2:2.4-1.1 restores it to work fine.
>
> I do not know how to configure ifupdown to disable random mac address
> usage just as how network-manager does in
> /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf .

So how about NM? Does it work for you if you use NM?

-- 
Cheers,
  Andrew

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

2017-12-09 Thread YOSHINO Yoshihito 
Package: wpasupplicant
Version: 2:2.6-13
Followup-For: Bug #833507

Dear Maintainer,

I use /etc/network/interfaces to configure networking, not network-manager.
Upgrading wpasupplicant to >= 2:2.6 my machine (MacBook Air with broadcom-sta
wl module) fails to connect to a wi-fi network, with a lot of syslog messages
of "CTRL-EVENT-SCAN-FAILED ret=-22".
Downgrading the package to 2:2.4-1.1 restores it to work fine.

I do not know how to configure ifupdown to disable random mac address
usage just as how network-manager does in
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf .

Regards,
-- 
YOSHINO Yoshihito 


-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8),
LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages wpasupplicant depends on:
ii  adduser   3.116
ii  libc6 2.25-3
ii  libdbus-1-3   1.12.2-1
ii  libnl-3-200   3.2.27-2
ii  libnl-genl-3-200  3.2.27-2
ii  libpcsclite1  1.8.22-1
ii  libreadline7  7.0-3
ii  libssl1.1 1.1.0g-2
ii  lsb-base  9.20170808

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn  libengine-pkcs11-openssl  
ii  wpagui2:2.6-13

-- no debconf information

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

2016-09-17 Thread 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)

2016-09-03 Thread 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)

2016-08-09 Thread 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)

2016-08-08 Thread 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

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

2016-08-05 Thread Support 
Package: wpasupplicant
Version: 2.5-2
Severity: important

Dear Maintainer,

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):

Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3827] device 
(wlan0): Activation: starting connection '' ()
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3829] audit: 
op="connection-activate" uuid="" name="" pid=6107 uid=1000 
result="success"
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3830] device 
(wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3848] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3851] device 
(wlan0): Activation: (wifi) access point '' has security, but secrets are 
required.
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3851] device 
(wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3897] device 
(wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3927] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3929] device 
(wlan0): Activation: (wifi) connection '' has security, and secrets 
exist.  No new secrets needed.
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3929] Config: 
added 'ssid' value ''
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3930] Config: 
added 'scan_ssid' value '1'
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3930] Config: 
added 'key_mgmt' value 'WPA-PSK'
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.3930] Config: 
added 'psk' value ''
Aug  5 11:17:29  NetworkManager[4695]:   [1470385049.4105] 
sup-iface[0xa1a4b0,wlan0]: config: set interface ap_scan to 1
Aug  5 11:17:29  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:30  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:31  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:32  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:33  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:34  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:35  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:36  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:37  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:38  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:39  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:40  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:41  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:42  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:43  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:44  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:45  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:46  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:47  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:48  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:49  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:50  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:51  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:52  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:53  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:54  wpa_supplicant[5054]: wlan0: CTRL-EVENT-SCAN-FAILED 
ret=-22 retry=1
Aug  5 11:17:54  NetworkManager[4695]:   [1470385074.7231] device 
(wlan0): Activation: (wifi) association took too long, failing activation
Aug  5 11:17:54  NetworkManager[4695]:   [1470385074.7232] device 
(wlan0): state change: config -> failed (reason 'ssid-not-found') [50 120 53]
Aug  5 11:17:54  NetworkManager[4695]:   [1470385074.7243] device 
(wlan0): Activation: failed for connection ''
Aug  5 11:17:54  NetworkManager[4695]:   [1470385074.7256] device 
(wlan0): state change: failed -> disconnected (reason 'none') [120 30 0]
Aug  5 11:17:54  NetworkManager[4695]:   [1470385074.7277] device 
(wlan0): supplicant interface state: inactive -> disconnected
Aug