Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#835553: network-manager: WiFi authentication fails after upgrade to 1.4.0

222 views
Skip to first unread message

Ben Caradoc-Davies

unread,
Aug 26, 2016, 10:10:02 PM8/26/16
to
Package: network-manager
Version: 1.2.4-2
Severity: normal

Dear Maintainer,

WiFi authentication fails after upgrading to network-manager 1.4.0. Workaround
is to downgrade to 1.2.4, which restores connection. This bug looks different
to #817123 as the device (external USB WiFi adapter) is detected and it appears
that only authentication is failing.

After these upgrades:

libnm-glib-vpn1:amd64 (1.2.4-2, 1.4.0-1),
libnm-glib4:amd64 (1.2.4-2, 1.4.0-1),
libnm-gtk-common:amd64 (1.2.4-1, 1.4.0-1),
libnm-gtk0:amd64 (1.2.4-1, 1.4.0-1)
libnm-util2:amd64 (1.2.4-2, 1.4.0-1),
libnm0:amd64 (1.2.4-2, 1.4.0-1),
libnma-common:amd64 (1.2.4-1, 1.4.0-1)
libnma0:amd64 (1.2.4-1, 1.4.0-1),
network-manager-gnome:amd64 (1.2.4-1, 1.4.0-1),
network-manager:amd64 (1.2.4-2, 1.4.0-1),

WiFi connection fails and daemon.log contains:

Aug 27 13:08:14 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
REENABLED id=0 ssid="yyyyyyyy"
Aug 27 13:08:14 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:08:19 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=2 duration=20
reason=CONN_FAILED
Aug 27 13:08:24 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:08:29 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=1 duration=10
reason=CONN_FAILED
Aug 27 13:08:40 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
REENABLED id=0 ssid="yyyyyyyy"
Aug 27 13:08:40 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:08:45 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=2 duration=20
reason=CONN_FAILED
Aug 27 13:13:50 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:13:56 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=1 duration=10
reason=CONN_FAILED
Aug 27 13:14:07 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
REENABLED id=0 ssid="yyyyyyyy"
Aug 27 13:14:07 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:14:12 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=2 duration=20
reason=CONN_FAILED
Aug 27 13:14:15 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:14:20 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=1 duration=10
reason=CONN_FAILED
Aug 27 13:14:31 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
REENABLED id=0 ssid="yyyyyyyy"
Aug 27 13:14:31 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:14:36 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=2 duration=20
reason=CONN_FAILED
Aug 27 13:14:41 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:14:46 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=1 duration=10
reason=CONN_FAILED
Aug 27 13:14:57 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
REENABLED id=0 ssid="yyyyyyyy"
Aug 27 13:14:57 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:15:02 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=2 duration=20
reason=CONN_FAILED
Aug 27 13:15:07 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:15:12 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=1 duration=10
reason=CONN_FAILED
Aug 27 13:15:23 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
REENABLED id=0 ssid="yyyyyyyy"
Aug 27 13:15:23 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:15:28 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-SSID-
TEMP-DISABLED id=0 ssid="yyyyyyyy" auth_failures=2 duration=20
reason=CONN_FAILED

After downgrading to:

libnm-glib-vpn1_1.2.4-2_amd64.deb
libnm-glib4_1.2.4-2_amd64.deb
libnm-gtk-common_1.2.4-1_all.deb
libnm-util2_1.2.4-2_amd64.deb
libnm0_1.2.4-2_amd64.deb
libnma-common_1.2.4-1_all.deb
libnma0_1.2.4-1_amd64.deb
network-manager-gnome_1.2.4-1_amd64.deb
network-manager_1.2.4-2_amd64.deb

Then:

systemctl restart NetworkManager.service

WiFi connection succeeds and daemon.log contains:

Aug 27 13:40:20 ripley wpa_supplicant[933]: wlxf4f26d10c509: SME: Trying to
authenticate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:40:21 ripley wpa_supplicant[933]: wlxf4f26d10c509: Trying to
associate with xx:xx:xx:xx:xx:xx (SSID='yyyyyyyy' freq=2462 MHz)
Aug 27 13:40:21 ripley wpa_supplicant[933]: wlxf4f26d10c509: Associated with
xx:xx:xx:xx:xx:xx
Aug 27 13:40:21 ripley wpa_supplicant[933]: wlxf4f26d10c509: WPA: Key
negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
Aug 27 13:40:21 ripley wpa_supplicant[933]: wlxf4f26d10c509: CTRL-EVENT-
CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed [id=0 id_str=]

Kind regards,
Ben.




-- 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/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii adduser 3.115
ii dbus 1.10.10-1
ii init-system-helpers 1.42
ii libaudit1 1:2.6.6-1
ii libbluetooth3 5.36-1+b2
ii libc6 2.23-5
ii libglib2.0-0 2.48.1-3
ii libgnutls30 3.5.3-3
ii libgudev-1.0-0 230-3
ii libmm-glib0 1.6.0-1
ii libndp0 1.6-1
ii libnewt0.52 0.52.18-3
ii libnl-3-200 3.2.27-1
ii libnm0 1.2.4-2
ii libpam-systemd 231-5
ii libpolkit-agent-1-0 0.105-16
ii libpolkit-gobject-1-0 0.105-16
ii libreadline6 6.3-8+b4
ii libselinux1 2.5-3
ii libsoup2.4-1 2.54.1-1
ii libsystemd0 231-5
ii libteamdctl0 1.24-1
ii libuuid1 2.28.1-1
ii lsb-base 9.20160629
ii policykit-1 0.105-16
ii udev 231-5
ii wpasupplicant 2.5-2+v2.4-2

Versions of packages network-manager recommends:
ii crda 3.13-1+b1
ii dnsmasq-base 2.76-3
ii iptables 1.6.0-3
ii iputils-arping 3:20150815-2
ii isc-dhcp-client 4.3.4-1
ii modemmanager 1.6.0-1
ii ppp 2.4.7-1+2

Versions of packages network-manager suggests:
pn libteam-utils <none>

-- no debconf information

Ben Caradoc-Davies

unread,
Aug 26, 2016, 10:40:03 PM8/26/16
to
I missed one package required for downgrade:

libnm-gtk0_1.2.4-1_amd64.deb

The full list of packages required to rescue an amd64 system:

libnm-glib-vpn1_1.2.4-2_amd64.deb
libnm-glib4_1.2.4-2_amd64.deb
libnm-gtk-common_1.2.4-1_all.deb
libnm-gtk0_1.2.4-1_amd64.deb
libnm-util2_1.2.4-2_amd64.deb
libnm0_1.2.4-2_amd64.deb
libnma-common_1.2.4-1_all.deb
libnma0_1.2.4-1_amd64.deb
network-manager-gnome_1.2.4-1_amd64.deb
network-manager_1.2.4-2_amd64.deb

These can be obtained from the pool and then installed with "dpkg -i":

http://ftp.debian.org/debian/pool/main/n/network-manager/
http://ftp.debian.org/debian/pool/main/n/network-manager-applet/

Fortunately USB tethering to a phone still works in 1.4.0.

Kind regards,

--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

Michael Biebl

unread,
Aug 27, 2016, 4:10:02 AM8/27/16
to
Am 27.08.2016 um 04:00 schrieb Ben Caradoc-Davies:
> Package: network-manager
> Version: 1.2.4-2
> Severity: normal
>
> Dear Maintainer,
>
> WiFi authentication fails after upgrading to network-manager 1.4.0. Workaround
> is to downgrade to 1.2.4, which restores connection. This bug looks different
> to #817123 as the device (external USB WiFi adapter) is detected and it appears
> that only authentication is failing.

Please report this issue upstream at
https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
(and report back with the bug number).

Thanks,
Michael


--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

signature.asc

Ben Caradoc-Davies

unread,
Aug 28, 2016, 12:40:03 AM8/28/16
to
Michael,

reported upstream as requested, including the new findings below:
https://bugzilla.gnome.org/show_bug.cgi?id=770504

Verbose debugging in wpa_supplicant reveals the presence of the scanning
MAC address 7E:19:8C:39:8B:F0 during authentication, despite a call
before authentication to set-hw-addr for the original MAC address
F4:F2:6D:10:C5:09. The MLME frame event is ignored as a foreign address
and authentication fails.

Aug 28 15:01:04 ripley NetworkManager[9018]: <info> [1472353264.6902]
device (wlxf4f26d10c509): set-hw-addr: set MAC address to
7E:19:8C:39:8B:F0 (scanning)
[...]
Aug 28 15:01:06 ripley NetworkManager[9018]: <info> [1472353266.3000]
device (wlxf4f26d10c509): set-hw-addr: set-cloned MAC address to
F4:F2:6D:10:C5:09 (permanent)
[...]
Aug 28 15:01:06 ripley wpa_supplicant[8462]: nl80211: New station
ec:cb:30:60:58:32
Aug 28 15:01:06 ripley wpa_supplicant[8462]: nl80211: Event message
available
Aug 28 15:01:06 ripley wpa_supplicant[8462]: nl80211: Drv Event 37
(NL80211_CMD_AUTHENTICATE) received for wlxf4f26d10c509
Aug 28 15:01:06 ripley wpa_supplicant[8462]: nl80211: MLME event 37
(NL80211_CMD_AUTHENTICATE) on wlxf4f26d10c509(7e:19:8c:39:8b:f0)
A1=f4:f2:6d:10:c5:09 A2=ec:cb:30:60:58:32
Aug 28 15:01:06 ripley wpa_supplicant[8462]: nl80211: wlxf4f26d10c509:
Ignore MLME frame event for foreign address

Workaround is to downgrade to 1.2.4.

Ben Caradoc-Davies

unread,
Aug 29, 2016, 7:40:03 PM8/29/16
to
Update, see: https://bugzilla.gnome.org/show_bug.cgi?id=770504

Workaround with 1.4.0 is to add this section to
/etc/NetworkManager/NetworkManager.conf:

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

With this setting and "systemctl restart NetworkManager.service", WiFi
authentication succeeds.

The upstream bug is a possible duplicate of:
https://bugzilla.gnome.org/show_bug.cgi?id=770456

I have supplied a log file and left it to the maintainers to decide.

Shreepad Shukla

unread,
Aug 21, 2017, 12:00:03 PM8/21/17
to
Hi

I have the same problem and the fix is the same as well, but the details are different:
- Debian Stretch 9.1 64 bit
- Linux 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64 GNU/Linux
- NetworkManager 1.6.2 
- wpa_supplicant v2.4 using driver nl80211 and firmware mt7601u.bin (installed from Debian non free package firmware-misc-nonfree)
- Device: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter (essentially a USB wifi dongle with an antenna)

Didn't mess around with any wpa supplicant conf or network config, just plugged in, set the password and monitored the daemon logs after setting the log level from the wpa_cli to msgdump.

In the daemon.log I get:

wpa_supplicant[590]: nl80211: Drv Event 37 (NL80211_CMD_AUTHENTICATE) received for wlxe...
wpa_supplicant[590]: nl80211: MLME event 37 (NL80211_CMD_AUTHENTICATE) on wlxe...(aa:bb:cc:dd:ee:ff) A1=11:22:33:44:55:66 A2=zz:ff:ee:dd:cc:bb
wpa_supplicant[590]: nl80211: wlxe...: Ignore MLME frame event for foreign address
wpa_supplicant[590]: wlxe...: SME: Authentication timeout

Workaround is to set wifi mac randomisation off in NetworkManager.conf as described above.
Have added the above on the upstream bug at https://bugzilla.gnome.org/show_bug.cgi?id=771966
Regards

Miguel A. Vallejo

unread,
Aug 30, 2017, 7:10:04 AM8/30/17
to
This bug seems to be even more problematic with kernel 4.12.0-1.


Kernel : 4.11.6-1
Firmware-misc-nonfree: 20170823-1
wpasupplicant: 2:2.4-1
Network Manager: 1.8.2-1
mac randomisation: ON
Device: Linksys WUSB600N v2 Dual-Band Wireless-N Network Adapter [Ralink RT3572]
Result: No connection


Kernel : 4.11.6-1
Firmware-misc-nonfree: 20170823-1
wpasupplicant: 2:2.4-1
Network Manager: 1.8.2-1
mac randomisation: OFF
Device: Linksys WUSB600N v2 Dual-Band Wireless-N Network Adapter [Ralink RT3572]
Result: Works like a charm

But with kernel 4.12.6-1 it is impossible to connect, no matter how is
mac randomisation. Same errors as before. Because everything stay the
same except the kernel maybe this is a kernel bug / regression.

Temporally I changed the device to an old D-Link System AirPlus G
DWL-G122 Wireless Adapter(rev.E1) [Ralink RT2070], and it just work
fine with mac randomisation off.

allan

unread,
Oct 15, 2017, 8:40:02 AM10/15/17
to
Confirmed still broken in Sid.  Disabling MAC randomization in NM also resolved the issue for me.
0 new messages