Bug#842422: network-manager: NetworkManager fails to authenticate with old 802.11bg USB devices

[peter]

From: "Miguel A. Vallejo" 
Date: Tue, 6 Dec 2016 14:19:26 +0100
> Something does not work with these new lng device names.

Interesting!  A few years back, when first making presistent names for 
Ethernet devices, I found that names longer than about 8 characters 
failed. Didn't investigate further and 8 is a weak approximation.  
The limit can just as well be 12.  Certainly would be wrong to impose 
such a limit for a name which can be based upon a MAC address.

Thanks,  ... Peter E.




-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca
https://en.wikibooks.org/wiki/Medical_Suction_Machines
https://en.wikibooks.org/wiki/Oberon

Bug#842422: network-manager: NetworkManager fails to authenticate with old 802.11bg USB devices

[Hillie Sample]

> add this to /etc/NetworkManager/NetworkManager.conf
> per bug #835553
>
> [device]
> wifi.scan-rand-mac-address=no

That worked for me with a Ralink Technology, Corp. RT5370 Wireless 
Adapter on Debian Stretch.  Thank you very much.

Bug#842422: network-manager: NetworkManager fails to authenticate with old 802.11bg USB devices

[Rask Ingemann Lambertsen]

Package: network-manager
Followup-For: Bug #842422

Dear Maintainer,

I just want to report that version 1.2.4-2 of network-manager works.
In my case, the affected network adapter is this USB device:

0846:6a00 NetGear, Inc. WG111v2 54 Mbps Wireless [RealTek RTL8187L] (rtl8187)

Bug#842422: network-manager: NetworkManager fails to authenticate with old 802.11bg USB devices

[Miguel A. Vallejo]

I just take a USB wifi adapter and tried to connect to my wireless network:





Dec  6 14:47:31 waterhole NetworkManager[562]:   [1481032051.7586]
keyfile: add connection in-memory (7c83331f-74b7-4ef8-98a5-
67bc03e24b36,"EOZWireless2")
Dec  6 14:47:31 waterhole NetworkManager[562]:   [1481032051.7954]
device (wlx1c7ee55ecc0a): Activation: starting connection 'EOZWireless2'
(7c83331f-74b7-4ef8-98a5-67bc03e24b36)
Dec  6 14:47:31 waterhole NetworkManager[562]:   [1481032051.8158]
keyfile: update /etc/NetworkManager/system-connections/EOZWireless2
(7c83331f-74b7-4ef8-98a5-67bc03e24b36,"EOZWireless2") and persist connection
Dec  6 14:47:31 waterhole NetworkManager[562]:   [1481032051.8160]
audit: op="connection-add-activate" uuid="7c83331f-74b7-4ef8-98a5-67bc03e24b36"
name="EOZWireless2" pid=1137 uid=1000 result="success"
Dec  6 14:47:31 waterhole NetworkManager[562]:   [1481032051.8213]
device (wlx1c7ee55ecc0a): state change: disconnected -> prepare (reason
'none') [30 40 0]
Dec  6 14:47:31 waterhole NetworkManager[562]:   [1481032051.8221]
manager: NetworkManager state is now CONNECTING
Dec  6 14:47:31 waterhole NetworkManager[562]:   [1481032051.8611]
device (wlx1c7ee55ecc0a): set-hw-addr: set-cloned MAC address to
1C:7E:E5:5E:CC:0A (permanent)
Dec  6 14:47:32 waterhole kernel: [  205.121018] IPv6: ADDRCONF(NETDEV_UP):
wlx1c7ee55ecc0a: link is not ready
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0483]
device (wlx1c7ee55ecc0a): state change: prepare -> config (reason 'none')
[40 50 0]
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0494]
device (wlx1c7ee55ecc0a): Activation: (wifi) access point 'EOZWireless2'
has security, but secrets are required.
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0505]
device (wlx1c7ee55ecc0a): state change: config -> need-auth (reason 'none')
[50 60 0]
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0575]
device (wlx1c7ee55ecc0a): state change: need-auth -> prepare (reason
'none') [60 40 0]
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0585]
device (wlx1c7ee55ecc0a): state change: prepare -> config (reason 'none')
[40 50 0]
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0592]
device (wlx1c7ee55ecc0a): Activation: (wifi) connection 'EOZWireless2' has
security, and secrets exist.  No new secrets needed.
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0598]
Config: added 'ssid' value 'EOZWireless2'
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0602]
Config: added 'scan_ssid' value '1'
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0605]
Config: added 'key_mgmt' value 'WPA-PSK'
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0605]
Config: added 'auth_alg' value 'OPEN'
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0605]
Config: added 'psk' value ''
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0625]
sup-iface[0x55680e8fe970,wlx1c7ee55ecc0a]: config: set interface ap_scan to
1
Dec  6 14:47:32 waterhole NetworkManager[562]:   [1481032052.0976]
device (wlx1c7ee55ecc0a): supplicant interface state: inactive -> scanning
Dec  6 14:47:36 waterhole wpa_supplicant[614]: wlx1c7ee55ecc0a: SME: Trying
to authenticate with 4c:60:de:6b:c3:0c (SSID='EOZWireless2' freq=5200 MHz)
Dec  6 14:47:36 waterhole kernel: [  209.921607] wlx1c7ee55ecc0a:
authenticate with 4c:60:de:6b:c3:0c
Dec  6 14:47:36 waterhole kernel: [  210.000312] wlx1c7ee55ecc0a: send auth
to 4c:60:de:6b:c3:0c (try 1/3)
Dec  6 14:47:36 waterhole kernel: [  210.001329] wlx1c7ee55ecc0a:
authenticated
Dec  6 14:47:36 waterhole NetworkManager[562]:   [1481032056.9302]
device (wlx1c7ee55ecc0a): supplicant interface state: scanning ->
authenticating
Dec  6 14:47:41 waterhole wpa_supplicant[614]: wlx1c7ee55ecc0a: SME: Deauth
request to the driver failed
Dec  6 14:47:41 waterhole NetworkManager[562]:   [1481032061.9310]
device (wlx1c7ee55ecc0a): supplicant interface state: authenticating ->
disconnected
Dec  6 14:47:42 waterhole NetworkManager[562]:   [1481032062.0313]
device (wlx1c7ee55ecc0a): supplicant interface state: disconnected ->
scanning
Dec  6 14:47:46 waterhole wpa_supplicant[614]: wlx1c7ee55ecc0a: SME: Trying
to authenticate with 4c:60:de:6b:c3:0c (SSID='EOZWireless2' freq=5200 MHz)
Dec  6 14:47:46 waterhole kernel: [  219.838794] wlx1c7ee55ecc0a:
authenticate with 4c:60:de:6b:c3:0c
Dec  6 14:47:46 waterhole kernel: [  219.916673] wlx1c7ee55ecc0a: send auth
to 4c:60:de:6b:c3:0c (try 1/3)
Dec  6 14:47:46 waterhole NetworkManager[562]:   [1481032066.8465]
device (wlx1c7ee55ecc0a): supplicant interface state: scanning ->
authenticating
Dec  6 14:47:46 waterhole kernel: [  219.920717] wlx1c7ee55ecc0a:
authenticated
Dec  6 14:47:51 waterhole wpa_supplicant[614]: wlx1c7ee55ecc0a: SME: Deauth
request to the driver failed
Dec  6 14:47:51 waterhole NetworkManager[562]:   [1481032071.8473]
device (wlx1c7ee55ecc0a): supplicant interface state: authenticating ->

Bug#842422: network-manager: NetworkManager fails to authenticate with old 802.11bg USB devices

[Miguel A. Vallejo]

Same problem here. Only fix I found is to use udev to rename device names
to the classic ones, for example wlan0.

I use /etc/udev/rules.d/70-persistent-net.rules

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:22:2f:c3:f6:2a", ATTR{dev_id}=="0x0", AT
TR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

In this way everything works nicely.

Something does not work with these new lng device names.

Bug#842422: network-manager: NetworkManager fails to authenticate with old 802.11bg USB devices

[Georg Colle]

Hi, got quite the same issues using network-manager 1.4.2-2,
network-manager-gnome 1.4.2-1, and wpasupplicant 2.5-2+v2.4-3+b1 trying to
connect dongles AVM FRITZ!Wlan N, D-Link DWA-160 B2, and ASUS USB-N53 to
the acces-points of routers Netgear DGND3800b and FRITZ!Box 7490.

Using networking.service together with appropriate /etc/network/interfaces
and wpa_supplicant could be useful as a workaround. At least this worked
for me in 2012 when I bought those dongles.

Greeting, Georg
-- 
... post tenebras spero lucem. (Hiob 17,12 Vul.)

Bug#842422: network-manager: NetworkManager fails to authenticate with old 802.11bg USB devices

[Vladimir Kudrya]

Package: network-manager
Version: 1.4.2-2
Severity: normal

Dear Maintainer, NetworkManager fails to connect to wireless network using 
802.11bg dongles.
The bug appeared somewhere around september upgrades on stretch (unfortunately, 
I can not pinpoint).

I am able to connect using wpa_supplicant directly:

# wpa_supplicant -i wlx  -c /tmp/wpapp 
Successfully initialized wpa_supplicant
wlx: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX 
(SSID='wlanssid' freq=2437 MHz)
wlx: Trying to associate with XX:XX:XX:XX:XX:XX 
(SSID='wlanssid' freq=2437 MHz)
wlx: Associated with XX:XX:XX:XX:XX:XX
wlx: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY 
alpha2=RU
wlx: WPA: Key negotiation completed with XX:XX:XX:XX:XX:XX 
[PTK=CCMP GTK=CCMP]
wlx: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:XX:XX 
completed [id=0 id_str=]
wlx: WPA: Group rekeying completed with XX:XX:XX:XX:XX:XX 
[GTK=CCMP]
wlx: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX:XX:XX 
reason=2 locally_generated=1
wlx: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlx: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX 
(SSID='wlanssid' freq=2437 MHz)
wlx: Trying to associate with XX:XX:XX:XX:XX:XX 
(SSID='wlanssid' freq=2437 MHz)
wlx: Associated with XX:XX:XX:XX:XX:XX
wlx: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY 
alpha2=RU
wlx: WPA: Key negotiation completed with XX:XX:XX:XX:XX:XX 
[PTK=CCMP GTK=CCMP]
wlx: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:XX:XX 
completed [id=0 id_str=]
wlx: WPA: Group rekeying completed with XX:XX:XX:XX:XX:XX 
[GTK=CCMP]
^Cwlx: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX:XX:XX 
reason=3 locally_generated=1
nl80211: deinit ifname=wlx disabled_11b_rates=0
wlx: CTRL-EVENT-TERMINATING

But when using NetworkManager, authentication fails:

Oct 29 02:09:02 hostname wpa_supplicant[22933]: wlx: SME: 
Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
Oct 29 02:09:02 hostname kernel: wlx: authenticate with 
XX:XX:XX:XX:XX:XX
Oct 29 02:09:02 hostname NetworkManager[8518]:   
[1477696142.2096] device (wlx): supplicant interface state: 
inactive -> authenticating
Oct 29 02:09:02 hostname kernel: wlx: send auth to 
XX:XX:XX:XX:XX:XX (try 1/3)
Oct 29 02:09:02 hostname kernel: wlx: authenticated
Oct 29 02:09:07 hostname kernel: wlx: aborting 
authentication with XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 29 02:09:07 hostname NetworkManager[8518]:   
[1477696147.2352] device (wlx): supplicant interface state: 
authenticating -> disconnected
Oct 29 02:09:07 hostname NetworkManager[8518]:   
[1477696147.3382] device (wlx): supplicant interface state: 
disconnected -> scanning
Oct 29 02:09:08 hostname wpa_supplicant[22933]: wlx: SME: 
Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
Oct 29 02:09:08 hostname kernel: wlx: authenticate with 
XX:XX:XX:XX:XX:XX
Oct 29 02:09:08 hostname kernel: wlx: send auth to 
XX:XX:XX:XX:XX:XX (try 1/3)
Oct 29 02:09:08 hostname NetworkManager[8518]:   
[1477696148.4705] device (wlx): supplicant interface state: 
scanning -> authenticating
Oct 29 02:09:08 hostname kernel: wlx: authenticated
Oct 29 02:09:13 hostname kernel: wlx: aborting 
authentication with XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 29 02:09:13 hostname NetworkManager[8518]:   
[1477696153.4989] device (wlx): supplicant interface state: 
authenticating -> disconnected
Oct 29 02:09:14 hostname NetworkManager[8518]:   
[1477696154.0034] device (wlx): supplicant interface state: 
disconnected -> scanning
Oct 29 02:09:15 hostname wpa_supplicant[22933]: wlx: SME: 
Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
Oct 29 02:09:15 hostname kernel: wlx: authenticate with 
XX:XX:XX:XX:XX:XX
Oct 29 02:09:15 hostname NetworkManager[8518]:   
[1477696155.1391] device (wlx): supplicant interface state: 
scanning -> authenticating
Oct 29 02:09:15 hostname kernel: wlx: send auth to 
XX:XX:XX:XX:XX:XX (try 1/3)
Oct 29 02:09:15 hostname kernel: wlx: authenticated
Oct 29 02:09:20 hostname wpa_supplicant[22933]: wlx: SME: 
Deauth request to the driver failed
Oct 29 02:09:20