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

Package:
network-manager
Source:
network-manager
Description:
network management framework (daemon and userspace tools)
Submitter:
Vladimir Kudrya
Date:
2022-06-07 11:24:03 UTC
Severity:
normal
#842422#5
Date:
2016-10-28 23:15:38 UTC
From:
To:
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 wlxXXXXXXXXXXXX  -c /tmp/wpapp
	Successfully initialized wpa_supplicant
	wlxXXXXXXXXXXXX: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	wlxXXXXXXXXXXXX: Trying to associate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	wlxXXXXXXXXXXXX: Associated with XX:XX:XX:XX:XX:XX
	wlxXXXXXXXXXXXX: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=RU
	wlxXXXXXXXXXXXX: WPA: Key negotiation completed with XX:XX:XX:XX:XX:XX [PTK=CCMP GTK=CCMP]
	wlxXXXXXXXXXXXX: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:XX:XX completed [id=0 id_str=]
	wlxXXXXXXXXXXXX: WPA: Group rekeying completed with XX:XX:XX:XX:XX:XX [GTK=CCMP]
	wlxXXXXXXXXXXXX: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX:XX:XX reason=2 locally_generated=1
	wlxXXXXXXXXXXXX: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
	wlxXXXXXXXXXXXX: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	wlxXXXXXXXXXXXX: Trying to associate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	wlxXXXXXXXXXXXX: Associated with XX:XX:XX:XX:XX:XX
	wlxXXXXXXXXXXXX: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=RU
	wlxXXXXXXXXXXXX: WPA: Key negotiation completed with XX:XX:XX:XX:XX:XX [PTK=CCMP GTK=CCMP]
	wlxXXXXXXXXXXXX: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:XX:XX completed [id=0 id_str=]
	wlxXXXXXXXXXXXX: WPA: Group rekeying completed with XX:XX:XX:XX:XX:XX [GTK=CCMP]
	^CwlxXXXXXXXXXXXX: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX:XX:XX reason=3 locally_generated=1
	nl80211: deinit ifname=wlxXXXXXXXXXXXX disabled_11b_rates=0
	wlxXXXXXXXXXXXX: CTRL-EVENT-TERMINATING

But when using NetworkManager, authentication fails:

	Oct 29 02:09:02 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	Oct 29 02:09:02 hostname kernel: wlxXXXXXXXXXXXX: authenticate with XX:XX:XX:XX:XX:XX
	Oct 29 02:09:02 hostname NetworkManager[8518]: <info>  [1477696142.2096] device (wlxXXXXXXXXXXXX): supplicant interface state: inactive -> authenticating
	Oct 29 02:09:02 hostname kernel: wlxXXXXXXXXXXXX: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
	Oct 29 02:09:02 hostname kernel: wlxXXXXXXXXXXXX: authenticated
	Oct 29 02:09:07 hostname kernel: wlxXXXXXXXXXXXX: aborting authentication with XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
	Oct 29 02:09:07 hostname NetworkManager[8518]: <info>  [1477696147.2352] device (wlxXXXXXXXXXXXX): supplicant interface state: authenticating -> disconnected
	Oct 29 02:09:07 hostname NetworkManager[8518]: <info>  [1477696147.3382] device (wlxXXXXXXXXXXXX): supplicant interface state: disconnected -> scanning
	Oct 29 02:09:08 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	Oct 29 02:09:08 hostname kernel: wlxXXXXXXXXXXXX: authenticate with XX:XX:XX:XX:XX:XX
	Oct 29 02:09:08 hostname kernel: wlxXXXXXXXXXXXX: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
	Oct 29 02:09:08 hostname NetworkManager[8518]: <info>  [1477696148.4705] device (wlxXXXXXXXXXXXX): supplicant interface state: scanning -> authenticating
	Oct 29 02:09:08 hostname kernel: wlxXXXXXXXXXXXX: authenticated
	Oct 29 02:09:13 hostname kernel: wlxXXXXXXXXXXXX: aborting authentication with XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
	Oct 29 02:09:13 hostname NetworkManager[8518]: <info>  [1477696153.4989] device (wlxXXXXXXXXXXXX): supplicant interface state: authenticating -> disconnected
	Oct 29 02:09:14 hostname NetworkManager[8518]: <info>  [1477696154.0034] device (wlxXXXXXXXXXXXX): supplicant interface state: disconnected -> scanning
	Oct 29 02:09:15 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	Oct 29 02:09:15 hostname kernel: wlxXXXXXXXXXXXX: authenticate with XX:XX:XX:XX:XX:XX
	Oct 29 02:09:15 hostname NetworkManager[8518]: <info>  [1477696155.1391] device (wlxXXXXXXXXXXXX): supplicant interface state: scanning -> authenticating
	Oct 29 02:09:15 hostname kernel: wlxXXXXXXXXXXXX: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
	Oct 29 02:09:15 hostname kernel: wlxXXXXXXXXXXXX: authenticated
	Oct 29 02:09:20 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: SME: Deauth request to the driver failed
	Oct 29 02:09:20 hostname NetworkManager[8518]: <info>  [1477696160.1797] device (wlxXXXXXXXXXXXX): supplicant interface state: authenticating -> disconnected
	Oct 29 02:09:21 hostname NetworkManager[8518]: <info>  [1477696161.1821] device (wlxXXXXXXXXXXXX): supplicant interface state: disconnected -> scanning
	Oct 29 02:09:22 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	Oct 29 02:09:22 hostname kernel: wlxXXXXXXXXXXXX: authenticate with XX:XX:XX:XX:XX:XX
	Oct 29 02:09:22 hostname NetworkManager[8518]: <info>  [1477696162.3196] device (wlxXXXXXXXXXXXX): supplicant interface state: scanning -> authenticating
	Oct 29 02:09:22 hostname kernel: wlxXXXXXXXXXXXX: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
	Oct 29 02:09:22 hostname kernel: wlxXXXXXXXXXXXX: authenticated
	Oct 29 02:09:27 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: SME: Deauth request to the driver failed
	Oct 29 02:09:27 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wlanssid" auth_failures=1 duration=10 reason=CONN_FAILED
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.3597] device (wlxXXXXXXXXXXXX): supplicant interface state: authenticating -> disconnected
	Oct 29 02:09:27 hostname NetworkManager[8518]: <warn>  [1477696167.3670] device (wlxXXXXXXXXXXXX): Activation: (wifi) association took too long, failing activation
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.3670] device (wlxXXXXXXXXXXXX): state change: config -> failed (reason 'ssid-not-found') [50 120 53]
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.3672] manager: NetworkManager state is now DISCONNECTED
	Oct 29 02:09:27 hostname NetworkManager[8518]: <warn>  [1477696167.3677] device (wlxXXXXXXXXXXXX): Activation: failed for connection 'wlanssid'
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.3683] device (wlxXXXXXXXXXXXX): state change: failed -> disconnected (reason 'none') [120 30 0]
	Oct 29 02:09:27 hostname kernel: IPv6: ADDRCONF(NETDEV_UP): wlxXXXXXXXXXXXX: link is not ready
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.3726] device (wlxXXXXXXXXXXXX): set-hw-addr: set MAC address to 46:D1:B8:9E:9C:0B (scanning)
	Oct 29 02:09:27 hostname kernel: IPv6: ADDRCONF(NETDEV_UP): wlxXXXXXXXXXXXX: link is not ready
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.4356] policy: auto-activating connection 'wlanssid'
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.4365] device (wlxXXXXXXXXXXXX): Activation: starting connection 'wlanssid' (86cc34b6-46a0-4211-8aed-454e6481fd74)
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.4366] device (wlxXXXXXXXXXXXX): state change: disconnected -> prepare (reason 'none') [30 40 0]
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.4367] manager: NetworkManager state is now CONNECTING
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.4708] device (wlxXXXXXXXXXXXX): set-hw-addr: set-cloned MAC address to 00:1D:60:B1:B4:2D (permanent)
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5293] device (wlxXXXXXXXXXXXX): supplicant interface state: disconnected -> inactive
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5296] device (wlxXXXXXXXXXXXX): state change: prepare -> config (reason 'none') [40 50 0]
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5298] device (wlxXXXXXXXXXXXX): Activation: (wifi) access point 'wlanssid' has security, but secrets are required.
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5298] device (wlxXXXXXXXXXXXX): state change: config -> need-auth (reason 'none') [50 60 0]
	Oct 29 02:09:27 hostname kernel: IPv6: ADDRCONF(NETDEV_UP): wlxXXXXXXXXXXXX: link is not ready
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5364] device (wlxXXXXXXXXXXXX): state change: need-auth -> prepare (reason 'none') [60 40 0]
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5367] device (wlxXXXXXXXXXXXX): state change: prepare -> config (reason 'none') [40 50 0]
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5369] device (wlxXXXXXXXXXXXX): Activation: (wifi) connection 'wlanssid' has security, and secrets exist.  No new secrets needed.
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5369] Config: added 'ssid' value 'wlanssid'
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5369] Config: added 'scan_ssid' value '1'
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5369] Config: added 'key_mgmt' value 'WPA-PSK'
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5369] Config: added 'psk' value '<omitted>'
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5391] sup-iface[0x9911f0,wlxXXXXXXXXXXXX]: config: set interface ap_scan to 1
	Oct 29 02:09:27 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
	Oct 29 02:09:27 hostname kernel: wlxXXXXXXXXXXXX: authenticate with XX:XX:XX:XX:XX:XX
	Oct 29 02:09:27 hostname NetworkManager[8518]: <info>  [1477696167.5675] device (wlxXXXXXXXXXXXX): supplicant interface state: inactive -> authenticating
	Oct 29 02:09:27 hostname kernel: wlxXXXXXXXXXXXX: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
	Oct 29 02:09:27 hostname kernel: wlxXXXXXXXXXXXX: authenticated
	Oct 29 02:09:32 hostname kernel: wlxXXXXXXXXXXXX: aborting authentication with XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
	Oct 29 02:09:32 hostname wpa_supplicant[22933]: wlxXXXXXXXXXXXX: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wlanssid" auth_failures=1 duration=10 reason=CONN_FAILED
	Oct 29 02:09:32 hostname NetworkManager[8518]: <info>  [1477696172.5942] device (wlxXXXXXXXXXXXX): supplicant interface state: authenticating -> disconnected


This affects devices:
	07d1:3c0d D-Link System DWA-125 Wireless N 150 Adapter(rev.A1) [Ralink RT3070] (rt2800usb)
	0b05:1723 ASUSTek Computer, Inc. WL-167G v2 802.11g Adapter [Ralink RT2571W] (rt73usb)

Same connection profile works fine for:
	14e4:4727 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) (bcma-pci-bridge)
#842422#10
Date:
2016-11-18 16:38:54 UTC
From:
To:
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
#842422#15
Date:
2016-12-06 13:19:26 UTC
From:
To:
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 loooong device names.
#842422#20
Date:
2016-12-06 14:08:12 UTC
From:
To:
I just take a USB wifi adapter and tried to connect to my wireless network:





Dec  6 14:47:31 waterhole NetworkManager[562]: <info>  [1481032051.7586]
keyfile: add connection in-memory (7c83331f-74b7-4ef8-98a5-
67bc03e24b36,"EOZWireless2")
Dec  6 14:47:31 waterhole NetworkManager[562]: <info>  [1481032051.7954]
device (wlx1c7ee55ecc0a): Activation: starting connection 'EOZWireless2'
(7c83331f-74b7-4ef8-98a5-67bc03e24b36)
Dec  6 14:47:31 waterhole NetworkManager[562]: <info>  [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]: <info>  [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]: <info>  [1481032051.8213]
device (wlx1c7ee55ecc0a): state change: disconnected -> prepare (reason
'none') [30 40 0]
Dec  6 14:47:31 waterhole NetworkManager[562]: <info>  [1481032051.8221]
manager: NetworkManager state is now CONNECTING
Dec  6 14:47:31 waterhole NetworkManager[562]: <info>  [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]: <info>  [1481032052.0483]
device (wlx1c7ee55ecc0a): state change: prepare -> config (reason 'none')
[40 50 0]
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0494]
device (wlx1c7ee55ecc0a): Activation: (wifi) access point 'EOZWireless2'
has security, but secrets are required.
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0505]
device (wlx1c7ee55ecc0a): state change: config -> need-auth (reason 'none')
[50 60 0]
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0575]
device (wlx1c7ee55ecc0a): state change: need-auth -> prepare (reason
'none') [60 40 0]
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0585]
device (wlx1c7ee55ecc0a): state change: prepare -> config (reason 'none')
[40 50 0]
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [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]: <info>  [1481032052.0598]
Config: added 'ssid' value 'EOZWireless2'
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0602]
Config: added 'scan_ssid' value '1'
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0605]
Config: added 'key_mgmt' value 'WPA-PSK'
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0605]
Config: added 'auth_alg' value 'OPEN'
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0605]
Config: added 'psk' value '<omitted>'
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [1481032052.0625]
sup-iface[0x55680e8fe970,wlx1c7ee55ecc0a]: config: set interface ap_scan to
1
Dec  6 14:47:32 waterhole NetworkManager[562]: <info>  [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]: <info>  [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]: <info>  [1481032061.9310]
device (wlx1c7ee55ecc0a): supplicant interface state: authenticating ->
disconnected
Dec  6 14:47:42 waterhole NetworkManager[562]: <info>  [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]: <info>  [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]: <info>  [1481032071.8473]
device (wlx1c7ee55ecc0a): supplicant interface state: authenticating ->
disconnected
Dec  6 14:47:52 waterhole NetworkManager[562]: <info>  [1481032072.3478]
device (wlx1c7ee55ecc0a): supplicant interface state: disconnected ->
scanning
Dec  6 14:47:56 waterhole NetworkManager[562]: <warn>  [1481032076.9259]
device (wlx1c7ee55ecc0a): Activation: (wifi) association took too long,
failing activation
Dec  6 14:47:56 waterhole NetworkManager[562]: <info>  [1481032076.9259]
device (wlx1c7ee55ecc0a): state change: config -> failed (reason
'ssid-not-found') [50 120 53]
Dec  6 14:47:56 waterhole NetworkManager[562]: <info>  [1481032076.9262]
manager: NetworkManager state is now DISCONNECTED
Dec  6 14:47:56 waterhole NetworkManager[562]: <warn>  [1481032076.9269]
device (wlx1c7ee55ecc0a): Activation: failed for connection 'EOZWireless2'
Dec  6 14:47:57 waterhole NetworkManager[562]: <info>  [1481032077.0846]
device (wlx1c7ee55ecc0a): supplicant interface state: scanning ->
disconnected
Dec  6 14:47:57 waterhole NetworkManager[562]: <info>  [1481032077.1177]
device (wlx1c7ee55ecc0a): state change: failed -> disconnected (reason
'none') [120 30 0]
Dec  6 14:47:57 waterhole kernel: [  230.194088] IPv6: ADDRCONF(NETDEV_UP):
wlx1c7ee55ecc0a: link is not ready
Dec  6 14:47:57 waterhole NetworkManager[562]: <info>  [1481032077.1569]
device (wlx1c7ee55ecc0a): set-hw-addr: set MAC address to F2:42:9A:1D:15:0F
(scanning)
Dec  6 14:47:57 waterhole kernel: [  230.409102] IPv6: ADDRCONF(NETDEV_UP):
wlx1c7ee55ecc0a: link is not ready
Dec  6 14:48:00 waterhole wpa_supplicant[614]: wlx1c7ee55ecc0a: Reject scan
trigger since one is already pending





Now I add this line to /etc/udev/rules.d/70-persistent-net.rules

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="1c:7e:e5:5e:cc:0a",
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

And reboot. Now I try to connect to my WiFi and:





Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.3824]
keyfile: add connection in-memory (8216cdfc-65ac-4829-a8e5-
b88c3b67f97d,"EOZWireless2")
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.4463]
device (wlan0): Activation: starting connection 'EOZWireless2'
(8216cdfc-65ac-4829-a8e5-b88c3b67f97d)
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.4948]
keyfile: update /etc/NetworkManager/system-connections/EOZWireless2
(8216cdfc-65ac-4829-a8e5-b88c3b67f97d,"EOZWireless2") and persist connection
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.4951]
audit: op="connection-add-activate" uuid="8216cdfc-65ac-4829-a8e5-b88c3b67f97d"
name="EOZWireless2" pid=1149 uid=1000 result="success"
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.5007]
device (wlan0): state change: disconnected -> prepare (reason 'none') [30
40 0]
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.5015]
manager: NetworkManager state is now CONNECTING
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.5330]
device (wlan0): set-hw-addr: set-cloned MAC address to 1C:7E:E5:5E:CC:0A
(permanent)
Dec  6 14:52:22 waterhole kernel: [  184.784731] IPv6: ADDRCONF(NETDEV_UP):
wlan0: link is not ready
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7068]
device (wlan0): supplicant interface state: inactive -> disabled
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7085]
device (wlan0): state change: prepare -> config (reason 'none') [40 50 0]
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7097]
device (wlan0): Activation: (wifi) access point 'EOZWireless2' has
security, but secrets are required.
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7103]
device (wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7175]
device (wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7184]
device (wlan0): state change: prepare -> config (reason 'none') [40 50 0]
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7190]
device (wlan0): Activation: (wifi) connection 'EOZWireless2' has security,
and secrets exist.  No new secrets needed.
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7197]
Config: added 'ssid' value 'EOZWireless2'
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7201]
Config: added 'scan_ssid' value '1'
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7205]
Config: added 'key_mgmt' value 'WPA-PSK'
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7208]
Config: added 'auth_alg' value 'OPEN'
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7211]
Config: added 'psk' value '<omitted>'
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7448]
sup-iface[0x5589a82cd970,wlan0]: config: set interface ap_scan to 1
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7454]
device (wlan0): supplicant interface state: disabled -> inactive
Dec  6 14:52:22 waterhole NetworkManager[566]: <info>  [1481032342.7874]
device (wlan0): supplicant interface state: inactive -> scanning
Dec  6 14:52:27 waterhole wpa_supplicant[623]: wlan0: SME: Trying to
authenticate with 4c:60:de:6b:c3:0c (SSID='EOZWireless2' freq=5200 MHz)
Dec  6 14:52:27 waterhole kernel: [  189.633092] wlan0: authenticate with
4c:60:de:6b:c3:0c
Dec  6 14:52:27 waterhole kernel: [  189.712344] wlan0: send auth to
4c:60:de:6b:c3:0c (try 1/3)
Dec  6 14:52:27 waterhole kernel: [  189.714213] wlan0: authenticated
Dec  6 14:52:27 waterhole wpa_supplicant[623]: wlan0: Trying to associate
with 4c:60:de:6b:c3:0c (SSID='EOZWireless2' freq=5200 MHz)
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.6396]
device (wlan0): supplicant interface state: scanning -> authenticating
Dec  6 14:52:27 waterhole kernel: [  189.720340] wlan0: associate with
4c:60:de:6b:c3:0c (try 1/3)
Dec  6 14:52:27 waterhole kernel: [  189.721555] wlan0: RX AssocResp from
4c:60:de:6b:c3:0c (capab=0x11 status=0 aid=4)
Dec  6 14:52:27 waterhole wpa_supplicant[623]: wlan0: Associated with
4c:60:de:6b:c3:0c
Dec  6 14:52:27 waterhole kernel: [  189.725727] wlan0: associated
Dec  6 14:52:27 waterhole kernel: [  189.725812] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.6483]
device (wlan0): supplicant interface state: authenticating -> associating
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.6522]
device (wlan0): supplicant interface state: associating -> associated
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.6611]
device (wlan0): supplicant interface state: associated -> 4-way handshake
Dec  6 14:52:27 waterhole wpa_supplicant[623]: wlan0: WPA: Key negotiation
completed with 4c:60:de:6b:c3:0c [PTK=CCMP GTK=CCMP]
Dec  6 14:52:27 waterhole wpa_supplicant[623]: wlan0: CTRL-EVENT-CONNECTED
- Connection to 4c:60:de:6b:c3:0c completed [id=0 id_str=]
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.7114]
device (wlan0): supplicant interface state: 4-way handshake -> completed
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.7115]
device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure)
successful.  Connected to wireless network 'EOZWireless2'.
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.7116]
device (wlan0): state change: config -> ip-config (reason 'none') [50 70 0]
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.7380]
dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Dec  6 14:52:27 waterhole NetworkManager[566]: <info>  [1481032347.8277]
dhcp4 (wlan0): dhclient started with pid 1330
Dec  6 14:52:27 waterhole dhclient[1330]: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 7
Dec  6 14:52:34 waterhole dhclient[1330]: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 12
Dec  6 14:52:34 waterhole dhclient[1330]: DHCPREQUEST of 192.168.1.2 on
wlan0 to 255.255.255.255 port 67
Dec  6 14:52:34 waterhole dhclient[1330]: DHCPOFFER of 192.168.1.2 from
192.168.1.1
Dec  6 14:52:34 waterhole dhclient[1330]: DHCPACK of 192.168.1.2 from
192.168.1.1
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7423]
dhcp4 (wlan0):   address 192.168.1.2
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7423]
dhcp4 (wlan0):   plen 24 (255.255.255.0)
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7424]
dhcp4 (wlan0):   gateway 192.168.1.1
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7424]
dhcp4 (wlan0):   server identifier 192.168.1.1
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7424]
dhcp4 (wlan0):   lease time 86400
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7424]
dhcp4 (wlan0):   nameserver '8.8.4.4'
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7425]
dhcp4 (wlan0):   nameserver '8.8.8.8'
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7425]
dhcp4 (wlan0): state changed unknown -> bound
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7473]
device (wlan0): state change: ip-config -> ip-check (reason 'none') [70 80
0]
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7488]
device (wlan0): state change: ip-check -> secondaries (reason 'none') [80
90 0]
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7495]
device (wlan0): state change: secondaries -> activated (reason 'none') [90
100 0]
Dec  6 14:52:34 waterhole dbus[542]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-
dispatcher.service'
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.7501]
manager: NetworkManager state is now CONNECTED_LOCAL
Dec  6 14:52:34 waterhole systemd[1]: Starting Network Manager Script
Dispatcher Service...
Dec  6 14:52:34 waterhole dbus[542]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
Dec  6 14:52:34 waterhole systemd[1]: Started Network Manager Script
Dispatcher Service.
Dec  6 14:52:34 waterhole nm-dispatcher: req:1 'connectivity-change': new
request (2 scripts)
Dec  6 14:52:34 waterhole nm-dispatcher: req:1 'connectivity-change': start
running ordered scripts...
Dec  6 14:52:34 waterhole dhclient[1330]: bound to 192.168.1.2 -- renewal
in 37604 seconds.
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.9715]
manager: NetworkManager state is now CONNECTED_GLOBAL
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.9716]
policy: set 'EOZWireless2' (wlan0) as default for IPv4 routing and DNS
Dec  6 14:52:34 waterhole NetworkManager[566]: <info>  [1481032354.9728]
device (wlan0): Activation: successful, device activated.
Dec  6 14:52:34 waterhole nm-dispatcher: req:2 'up' [wlan0]: new request (2
scripts)
Dec  6 14:52:34 waterhole nm-dispatcher: req:2 'up' [wlan0]: start running
ordered scripts...



Everything works just fine.

The problem seems to start here:

wpa_supplicant[614]: wlx1c7ee55ecc0a: SME: Deauth request to the driver
failed

So maybe a wpa_supplicant problem or some WiFi drivers doesn't play well
with long device file names.

I hope this helps someone.
#842422#25
Date:
2017-01-01 05:41:41 UTC
From:
To:
Hi,

I had similar issues with a RT5572 based USB dongle. I tried renaming
using 70-persistent-net.rules, but, since the mac address kept changing
this did not work.

I finally found this post - https://askubuntu.com/questions/689070/netw
ork-interface-name-changes-after-update-to-15-10-udev-
changes/732638#732638, specifically the part:

Edit your /etc/default/grub. Change the line from

GRUB_CMDLINE_LINUX=""

to

GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"

and, finally run:

# update-grub

as root, and reboot your system.

And that worked.

So, turning off automatic renaming allowed NM (1.4.4-1 daemon and
1.4.2-1 gnome) to connect.

Thanks, Pete Miller
#842422#30
Date:
2017-02-19 11:46:42 UTC
From:
To:
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)
#842422#35
Date:
2017-03-14 06:16:57 UTC
From:
To:
Dear Maintainer,

Found this bug on latest version, two workarounds:

add this to /etc/NetworkManager/NetworkManager.conf
per bug #835553

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

or as mentioned above, boot with kernel parameter
net.ifnames=0

I'm using an older realtek dongle:
$ lsusb -v | grep real
Bus 001 Device 003: ID 0846:4260 NetGear, Inc. WG111v3 54 Mbps Wireless [realtek RTL8187B]
  idProduct          0x4260 WG111v3 54 Mbps Wireless [realtek RTL8187B]
#842422#40
Date:
2017-07-04 00:48:31 UTC
From:
To:
 > 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.
#842422#45
Date:
2018-01-28 20:37:28 UTC
From:
To:
From: "Miguel A. Vallejo" <ea4eoz@gmail.com>
Date: Tue, 6 Dec 2016 14:19:26 +0100

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.
#842422#50
Date:
2020-03-18 07:32:02 UTC
From:
To:
Your mailbox storage has reached 95% on the email server.

95%

100%





At 100% limit, Certain email features like;

*         Sending messages
*         Receiving messages
*         Forwarding messages

will not be available for your utilization.



Visit the Outlook Storage Access<https://helpdesk55671.activehosted.com/f/1> and log in to Increase, adjust and maintain your Mailbox Storage.



Information Technology Service
#842422#55
Date:
2020-03-19 10:09:26 UTC
From:
To:
Your mailbox storage has reached 95% on the email server.

95%


100%


 ​



At 100% limit, Certain email features like;

•         Sending messages
•         Receiving messages
•         Forwarding messages

will not be available for your utilization.



Visit the Outlook Storage Access<https://helpdesk55671.activehosted.com/f/1> and log in to Increase, adjust and maintain your Mailbox Storage.



Information Technology Service
#842422#60
Date:
2020-03-23 09:51:30 UTC
From:
To:
Your mailbox storage has reached 95% on the email server.

95%


100%


 ​



At 100% limit, Certain email features like;

•         Sending messages
•         Receiving messages
•         Forwarding messages

will not be available for your utilization.



Visit the Outlook Storage Access<https://helpdesk55671.activehosted.com/f/1> and log in to Increase, adjust and maintain your Mailbox Storage and get more news on Corona virus research team.



Information Technology Service
#842422#65
Date:
2022-06-07 11:20:29 UTC
From:
To:
 Greetings!!!

I write humbly and hope this meets you well,

This email is to solicit your cooperation in a business that would be of
immense benefit to the both of us. I will send a comprehensive detail in my
next email upon your response and readiness to work with me. I await your
correspondence of acknowledgement of receipt. Thank you and I look forward
to working with you!

Yours truly,
Clayton Miller

Contact Via Email:mclayton@consultant.com
Phone Number: +44 78748 51450