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

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

My wlan chip is a "Broadcom Corporation BCM43142 802.11b/g/n (rev 01)" (Dell VOSTRO), so
i have to use the non-free package broadcom-sta-dkms.

Regrads, Robert

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wpasupplicant depends on:
ii adduser 3.115
ii libc6 2.23-4
ii libdbus-1-3 1.10.8-1
ii libnl-3-200 3.2.27-1
ii libnl-genl-3-200 3.2.27-1
ii libpcsclite1 1.8.17-1
ii libreadline6 6.3-8+b4
ii libssl1.0.2 1.0.2h-1
ii lsb-base 9.20160629

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn libengine-pkcs11-openssl <none>
pn wpagui <none>

-- no debconf information

[Andrew Shadura]

Post by Support
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

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.

[Noël Köthe]

Package: wpasupplicant
Version: 2:2.6-11
Followup-For: Bug #833507

Dear Maintainer,

with one of the sid updates last week my wireless stop
working again with the
wpa_supplicant[737]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0

I remember a workaround for this problem from the past to add
into /etc/NetworkManager/NetworkManager.conf the following:

[device]
wifi.scan-rand-mac-address=no

which fixed it again for me.

...
network-manager (1.4.0-4) unstable; urgency=medium
...
* Fix MAC address randomization.
Cherry-pick a couple of upstream commits which work around driver bugs
when MAC address randomization is used. (Closes: #835822, #835553)
...

Because the last network-manager was from 2017-11-10 and my wlan problem
started last week I'm a bit unsure where the root cause is.

Maybe the workaround helps someone.

Regards

Noël

-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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 <none>
pn wpagui

[Andrew Shadura]

Hello Andrew,

Post by Noël Köthe
I remember a workaround for this problem from the past to add
[device]
wifi.scan-rand-mac-address=no
which fixed it again for me.

Just to be sure, are you absolutely sure it doesn't work with the
latest wpasupplicant without the NM snippet?

Yes. Wifi worked until Tue or Wed last week and with my daily sid
update I didn't get it working again. Module unloading and loading or
network-manager restarts or complete reboots didn't helped.
Until yesterday when I added the NM lines again.

Thanks.

I have put a similar one
into the wpasupplicant package, but a driver-specific one.

OK.

Could you please let me know what driver are you using?

wl module/driver with the broadcom-sta-dkms 6.30.223.271-7
03:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless
Network Adapter (rev 03) on a MacBook Pro
03:00.0 0280: 14e4:43a0 (rev 03)

nmcli -f GENERAL.DRIVER,GENERAL.DRIVER-VERSION device show

# nmcli -f GENERAL.DRIVER,GENERAL.DRIVER-VERSION device show
GENERAL.DRIVER: tg3
GENERAL.DRIVER-VERSION: 3.137
GENERAL.DRIVER: wl
GENERAL.DRIVER-VERSION: 6.30.223.271 (r587334)

Right, so it is wl indeed.

GENERAL.DRIVER: bridge
GENERAL.DRIVER-VERSION: 2.3
GENERAL.DRIVER: unknown
GENERAL.DRIVER-VERSION: --
GENERAL.DRIVER: tun
GENERAL.DRIVER-VERSION: 1.6

Please bear in mind the file I'm shipping doesn't work with old NM,
what version are you using?

network-manager 1.10.0-1

This should be recent enough.

It is a sid system with no package on hold.
If I can help you with more information just tell me.

Thanks. Please have a look at
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.

There should be a line:

match-device=driver:rtl8723bs,…

Please add driver:wl to this comma-separated list, remove your previos
NetworkManager.conf addition, restart NM and try again. If this helps,
we can close the bug. If it doesn't, please check whether the config is
being parsed at all by runnin /usr/sbin/NetworkManager --print-config.

Thanks!

[Noël Köthe]

Hello Andrew,

Post by Andrew Shadura

If I can help you with more information just tell me.

Thanks. Please have a look at
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.
match-device=driver:rtl8723bs,

Please add driver:wl to this comma-separated list, remove your
previos NetworkManager.conf addition, restart NM and try again. If
this helps, we can close the bug. If it doesn't, please check whether
the config is being parsed at all by runnin /usr/sbin/NetworkManager
--print-config.

I can confirm, that removing the workaround in
/etc/NetworkManager/NetworkManager.conf and adding driver:wl into
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf as you described
it, gives me a working wifi network.

Regards

Noël

[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 <***@gmail.com>


-- 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 <none>
ii wpagui 2:2.6-13

-- no debconf information

[Kamil Jońca]

I can confirm, that upgrade wpasupplicant:amd64 (2:2.4-1, 2:2.6-13)
breaks wireless networking.
I have NO network manager.
there were no other changes (broadcom drivers or firmware)

downgraded wpasupplicant works like a charm.

KJ

[Rebekah Issah]

Hallo,

Bitte ist es in Ordnung, auf Englisch zu kommunizieren? Ich habe Google
Übersetzer verwendet, um Englisch zum besseren VerstÀndnis in Ihre Sprache
zu ÃŒbersetzen.

Ich bin Frau Rebekah Issah, eine Jemenfrau. Ich möchte wegen der
anhaltenden Unruhen / Kriege im Jemen sowie der tÀglichen
lebensbedrohlichen Angriffe von Al-Qaida-KÀmpfern nach Deutschland
umziehen. Ich habe meine Familie, meinen Mann, meinen Sohn und meine
Tochter bereits wÀhrend eines Angriffs auf unser Haus am 23. MÀrz 2019 an
die kalten HÀnde des Todes verloren, um unsere Familie zu beenden. Ich war
wÀhrend des Kreuzfeuers nicht da. Ich war zur Untersuchung im Krankenhaus,
als sie unser Haus angriffen, meinen geliebten Ehemann, Sohn und meine
Tochter töteten und das Haus in Brand steckten. Ich bin in TrÀnen, wenn ich
dir diese Mail schreibe. Er (mein verstorbener Ehemann) war ein sehr
erfolgreicher Bauunternehmer in der Ölstadt Jemen und beschÀftigte sich vor
seinem frÃŒhen Tod privat mit Goldstaub und Goldbarren. ErwartungsgemÀß hat
er einen angemessenen Geldbetrag zurÃŒckgelassen, den ich in den
Immobiliensektor, Reisen & Tourismus, Hotelmanagement und andere
interessante Sektoren in Deutschland investieren möchte.

Wie Sie vielleicht wissen oder nicht wissen, haben die von den Vereinigten
Staaten und der EuropÀischen Union verhÀngten Sanktionen es nahezu
unmöglich gemacht, hier im Jemen irgendeine Art von Investition erfolgreich
durchzufÃŒhren oder sogar Geld von hier in andere Teile der Welt zu
ÃŒberweisen. Aus diesem Grund kontaktiere ich Sie sehr zuversichtlich mit
der Hoffnung, dass Sie mir helfen können, dieses Geld fÌr
Investitionszwecke nach Deutschland zu bringen:

Bitte ich wÌrde gerne wissen, wie bequem es fÌr Sie sein könnte, mir auf
diese Weise zu helfen. Das gesamte mir zur VerfÃŒgung stehende Kapital
betrÀgt neun Millionen Euro. Ich habe das Geld heimlich in einem Kofferraum
eingesperrt und beim Roten Kreuz hier in Sanaa deponiert. Ich möchte Sie
aufrichtig schriftlich bitten, die SparbÃŒchse freundlich anzunehmen. Dies
liegt daran, dass wir nach dem Krieg von hier aus keine BankÃŒberweisungen
mehr durchfÌhren können. Dies sind die Hauptprobleme, die mich jetzt
beschÀftigen. Ich werde Ihnen 20% des Gesamtgeldes als Vorteil fÌr Ihre
Hilfe geben.

Ich muss diese Chance nutzen, weil ich keine andere Alternative habe, als
jemandem zu vertrauen. Ich kann mein Leben hier nicht riskieren, um ein
Ende meiner Familienlinie zu vermeiden. Als Frau ist mein Mann, mein Sohn
und meine Tochter tot. Ich verdiene ein anstÀndiges Leben in einer
friedlichen Umgebung. Ich werde nach Deutschland ziehen und das Geld in
Übereinstimmung mit dem Gesetz, Ihrem Rat und Ihrer UnterstÃŒtzung
investieren. wir können zusammenarbeiten und erreichen.

Ich erwarte Ihre positive Antwort und werde Ihnen nach Erhalt Ihrer
Informationen weitere Einzelheiten mitteilen.

Hochachtungsvoll,

Rebekah Issah.