NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

rabaimorp · 2024-10-17 18:02:29

After a NetworkManager update I can't use the following command if I'm trying to connect to a known network, I get this error

$ nmcli device wifi connect <SSID> password <password>
Error: 802-11-wireless-security.key-mgmt: property is missing.

Now I'm only able to use "nmcli connection up <SSID>" for know networks.
I also noticed that my connection is way more unstable, and the networks becomes unavailable for about 40 seconds every few hours, and sometimes it goes blank indefinetly until I reconnect. I went back to version 1.48.6-1 and it fixed every problem I had with the newer versions. Should I just stay on this version forever or...?

Evil_Hamster · 2024-10-19 20:43:55

Have/Had the same problem, and we are not the only ones. I also found
https://www.reddit.com/r/archlinux/comm … n_kind_of/
where the following

I've been having similar issues for months. Turns out the issue was not NetworkManager but rather the wifi backend. I'm assuming you are using wpa_supplicant. Try either downgradeing and/or switching NetworkManager to use iwd as the backend https://wiki.archlinux.org/title/Networ … Fi_backend

was proposed by VALTIELENTINE
. I cant say that it helped me, but it might help you.

philo · 2024-10-21 11:04:48

. Deleted any existing (but not working) wifi connection listed in nm-connection-editor.
. Installed iwd but did not enable the service nor configure it.
. Created the conf file :
/etc/NetworkManager/conf.d/wifi_backend.conf
as mentioned in the wiki link above (§7.12).
. Checked 'Enable wi-fi' option in nm-connection-editor and let it create a wifi connection.
. Done.

PS - It helped me… Did it help anyone else?

Last edited by philo (2024-10-22 11:12:31)

rabaimorp · 2024-10-23 17:24:33

philo wrote:

. Deleted any existing (but not working) wifi connection listed in nm-connection-editor.
. Installed iwd but did not enable the service nor configure it.
. Created the conf file :
/etc/NetworkManager/conf.d/wifi_backend.conf
as mentioned in the wiki link above (§7.12).
. Checked 'Enable wi-fi' option in nm-connection-editor and let it create a wifi connection.
. Done.
PS - It helped me… Did it help anyone else?

What's weird is that downgrading NetworkManager fixed the issue, not wpa_supplicant. It broke after a networkmanager update as well.

ttrreevvoorr · 2024-11-07 21:54:39

When I run the following command, I get this error also: `Error: 802-11-wireless-security.key-mgmt: property is missing.`
`$ nmcli device wifi connect <SSID> password <password>`

But when I run this with --ask instead, and provide the wifi password, I am able to connect.
`$ nmcli device wifi connect <SSID> --ask`

This is on nmcli version 1.50.0-1

Hope this helps someone.

Last edited by ttrreevvoorr (2024-11-07 21:54:58)

gustaw.daniel@gmail.com · 2024-11-13 07:29:26

I have access to 2 arch linux desktops and see this error on one of them but not on second so I will try to provide details to reproduction.

It works for:

nmcli --version
nmcli tool, version 1.48.6-1

but i getting error `Error: 802-11-wireless-security.key-mgmt: property is missing.` for

nmcli --version
nmcli tool, version 1.50.0-1

it works for

pacman -Q | grep 'networkmanager\|wpa_supplicant\|iwd'
iwd 3.1-1
networkmanager 1.48.6-1
wpa_supplicant 2:2.11-2

but is broken for

pacman -Q | grep 'networkmanager\|wpa_supplicant\|iwd'
iwd 3.1-1
networkmanager 1.50.0-1
wpa_supplicant 2:2.11-2

in both cases i have network

cat /etc/NetworkManager/system-connections/Sandro.nmconnection

[connection]
id=Sandro
uuid=4f4d7d6b-3c05-4c64-b6ca-bf47183ba0a8
type=wifi
interface-name=wlan0
timestamp=1731223044

[wifi]
mode=infrastructure
ssid=Sandro

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=xxx

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

[proxy]

seth · 2024-11-13 15:02:13

Please use [code][/code] tags. Edit your post in this regard.

is broken for … in both cases i have network

Is there some actual misfunction or are you reporting some stray error message out of context but everything end up working fine?

gustaw.daniel@gmail.com · 2024-11-17 13:00:15

I reproduced this problem for 2 different wifi networks on one of laptops, but there are some networks that still works.

seth · 2024-11-17 14:20:31

Networks w/ presumingly pre-stored credentials (ie NM would already know the WPA key)?

ttrreevvoorr wrote:

But when I run this with --ask instead, and provide the wifi password, I am able to connect.
`$ nmcli device wifi connect <SSID> --ask`

hjvt.dev · 2024-12-11 15:45:42

I've been experiencing this issue for about a month by now. One interesting thing is that `nmcli connection edit` -> `print 802-11-wireless-security` does report `key-mgmt` as present.

stellarium · 2024-12-12 12:34:05

I've had this issue for a few days now! (and I update relatively often)
I can connect to my 5G network but when it tries to connect to the 2.4ghz it just spews out this error.
I wonder what caused this?

stellarium · 2024-12-12 12:47:55

Just tried to connect again after downgrading to 1.48.6-1 and still having the same problem.
Either I get this error or the wifi can't be found. Even though it is detected and using BSSID just one number change makes it go from the 2.4ghz to 5G so I have 0 clue.

seth · 2024-12-12 20:13:01

does report `key-mgmt` as present

Which is likely the bug here?
Did you try to delete the connection and re-create it?

Esp. @stellarium
Did you check

$ nmcli device wifi connect <SSID> --ask

for the 2.4GHz network?

hjvt.dev · 2024-12-13 19:27:23

seth wrote:

Did you try to delete the connection and re-create it?

Yes, deleting the connection is a work-around, but next time I try to connect to a network that already has a connection, it breaks.

And another thing is that automatic re-connection in case of waking laptop from sleep or rebooting does work.

seth · 2024-12-13 22:02:41

Yes, deleting the connection is a work-around, but next time I try to connect to a network that already has a connection, it breaks.

Ie. you delete the connection, connect (works), disconnect, re-connect to the same network again and it now breaks again?
Ie. you cannot cure connections by deleting and recreating them?

I suspect this is related to how NM stores the network key and whether something like kwallet or gnome-keyring is involved.

olliv3r · 2024-12-15 18:17:20

So is this issue resolved at all?

I've been having this for months now too; on the network-manager gnome front end, I just get an authentication failure error. In the logs, I see:

dec 14 18:38:20 2of9 wpa_supplicant[759]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
dec 14 18:38:21 2of9 NetworkManager[682]: <info>  [1734197901.0390] device (wlp3s0): supplicant interface state: disconnected -> scanning
dec 14 18:38:21 2of9 NetworkManager[682]: <info>  [1734197901.0390] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> scanning
dec 14 18:38:33 2of9 wpa_supplicant[759]: wlp3s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="myssid"
dec 14 18:38:33 2of9 wpa_supplicant[759]: wlp3s0: BSSID 14:cc:20:8a:15:23 ignore list count incremented to 3, ignoring for 60 seconds
dec 14 18:38:33 2of9 wpa_supplicant[759]: wlp3s0: Trying to associate with SSID 'myssid'
dec 14 18:38:33 2of9 NetworkManager[682]: <info>  [1734197913.1063] device (wlp3s0): supplicant interface state: scanning -> associating
dec 14 18:38:33 2of9 NetworkManager[682]: <info>  [1734197913.1064] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> associating
dec 14 18:38:33 2of9 wpa_supplicant[759]: wlp3s0: Associated with 14:cc:20:8a:1a:c9
dec 14 18:38:33 2of9 wpa_supplicant[759]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
dec 14 18:38:33 2of9 NetworkManager[682]: <info>  [1734197913.1592] device (wlp3s0): supplicant interface state: associating -> associated
dec 14 18:38:33 2of9 NetworkManager[682]: <info>  [1734197913.1593] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> associated
dec 14 18:38:36 2of9 NetworkManager[682]: <warn>  [1734197916.0340] device (wlp3s0): Activation: (wifi) association took too long
dec 14 18:38:36 2of9 NetworkManager[682]: <info>  [1734197916.0342] device (wlp3s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
dec 14 18:38:36 2of9 NetworkManager[682]: <warn>  [1734197916.0354] device (wlp3s0): Activation: (wifi) asking for new secrets
dec 14 18:38:36 2of9 wpa_supplicant[759]: nl80211: send_event_marker failed: Source based routing not supported
dec 14 18:38:36 2of9 wpa_supplicant[759]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=14:cc:20:8a:1a:c9 reason=3 locally_generated=1
dec 14 18:38:36 2of9 wpa_supplicant[759]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
dec 14 18:38:36 2of9 NetworkManager[682]: <info>  [1734197916.0386] device (wlp3s0): supplicant interface state: associated -> disconnected

What's more confusing, is that this failing also happens on the latest arch live iso. BUT, if i use iwd in the live iso (or through a docker container!) just like with an Ubuntu (and also MacOS, this is a macbook pro from 2015) it works just fine. What's worse, I plug in some cheapy USB WiFi module, everthing works fine too.

The wpa_supplicant story seems to check out too; because when I'm at work (but also confirmed it with my phone at home) I connect to the open guest network, which doesn't require authentication, and that too works!

So where to start reporting bugs? I tried wiping all my network configs without success. Didn't try finding any wpa_supplicant configs yet though ..

seth · 2024-12-15 20:13:05

BUT, if i use iwd in the live iso (or through a docker container!) … it works just fine.

Same w/ https://wiki.archlinux.org/title/Networ … Fi_backend or is "use iwd" more like "not use networkmanager"?

hjvt.dev · 2024-12-18 11:10:02

seth wrote:

or is "use iwd" more like "not use networkmanager"?

I'd expect the latter, since I've tried switching NM to using `iwd`, and the issue persisted.

seth · 2024-12-18 13:57:50

=> Disable NM, try to use only iwd on the installed system to confirm that theory - though I heavily suspect that's gonna result in some keyring/wallet related issue

olliv3r · 2024-12-18 21:30:09

So a little bit more info, I ran just wpa_supplicant with the debugging flags, and found the following

[root@2 wpa_supplicant]# cat > /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/run/wpa_supplicant
update_config=1
[root@2 wpa_supplicant]# /usr/bin/wpa_supplicant -u -ddd -O /run/wpa_supplicant -i wlp3s0 -c /etc/wpa_supplicant/wpa_supplicant.conf

wlp3s0: Associated with 12:34
CTRL-DEBUG: ctrl_sock-sendmsg: sock=13 sndbuf=212992 outq=0 send_len=33
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_16935-2\x00
wlp3s0: WPA: Association event - clear replay counter
wlp3s0: WPA: Clear old PTK
TDLS: Remove peers on association
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
wlp3s0: Setting authentication timeout: 10 sec 0 usec
wlp3s0: Cancelling scan request
wlp3s0: ASSOC INFO: wait for driver port authorized indication
wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
CTRL-DEBUG: ctrl_sock-sendmsg: sock=13 sndbuf=212992 outq=0 send_len=40
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_16935-2\x00
RTM_NEWLINK: ifi_index=19 ifname=wlp3s0 wext ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK: ifi_index=19 ifname=wlp3s0 wext ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK: ifi_index=19 ifname=wlp3s0 wext ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
Control interface recv command from: /tmp/wpa_ctrl_16935-1\x00
wlp3s0: Control interface command 'PING'
CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=5
Control interface recv command from: /tmp/wpa_ctrl_16935-1\x00
wlp3s0: Control interface command 'PING'
CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=5
wlp3s0: Authentication with 12:34 timed out.
CTRL-DEBUG: ctrl_sock-sendmsg: sock=13 sndbuf=212992 outq=0 send_len=48
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_16935-2\x00
wlp3s0: Added BSSID 12:34 into ignore list, ignoring for 10 seconds
CTRL-DEBUG: ctrl_sock-sendmsg: sock=13 sndbuf=212992 outq=768 send_len=71
CTRL_IFACE monitor sent successfully to /tmp/wpa_ctrl_16935-2\x00
TDLS: Remove peers on disassociation
wlp3s0: WPA: Clear old PMK and PTK
wlp3s0: Request to deauthenticate - bssid=12:34 pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING) state=ASSOCIATED valid_links=0x0 ap_mld_addr=00:00:00:00:00:00
TDLS: Tear down peers
wpa_driver_nl80211_disconnect(reason_code=3)
nl80211: send_event_marker failed: Source based routing not supported
wlp3s0: Event DEAUTH (11) received
wlp3s0: Deauthentication notification
wlp3s0:  * reason 3 (DEAUTH_LEAVING) locally_generated=1
Deauthentication frame IE(s) - hexdump(len=0): [NULL]
wlp3s0: CTRL-EVENT-DISCONNECTED bssid=12:34 reason=3 locally_generated=1

I got this from wpa connect debug; though I don't think this contains anything useful ...

And for what it's worth, switching to iwd backend works splendidly.

Last edited by olliv3r (2024-12-20 11:47:35)

seth · 2024-12-18 21:48:06

Please use [code][/code] tags. Edit your post in this regard.
You're not getting key-mgmt related errors at all? But first an association and then an authentication timeout.
And this also seems to be wext (which would explain iwd and the wifi dongle behaving differently)

=> actually try the iwd NM backend

olliv3r · 2024-12-20 11:48:16

Sadly, iwd is also not ideal; In that I noticed after a few suspend/resumes, iwd failed to auth; using iwctl didn't help, but stopping network manager made it worked fine. A reboot also work though; so I'll keep an eye on this.

Last edited by olliv3r (2024-12-20 18:15:01)

seth · 2024-12-20 14:40:43

using iwctl didn't help, but stopping network manager made it worked

Running and iwd service AND networkmanager doesn't work anyway and just causes chaos.
Manual iwd/iwctl use implies to kill all other network managing daemons and

A reboot also worked though

basically proves that you're off-topic here.
Please open your own thread and post a complete system journal for an affected boot and certainly the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

there…

olliv3r · 2024-12-20 18:18:32

seth wrote:

using iwctl didn't help, but stopping network manager made it worked
Running and iwd service AND networkmanager doesn't work anyway and just causes chaos.

I appologize if I made you think this, but no; iwd is being used as the network-manager backend; but nm keeps iwd running of course, and connecting the nwcli to the running daemon is/should be fine?

seth wrote:

Manual iwd/iwctl use implies to kill all other network managing daemons and
A reboot also worked though
basically proves that you're off-topic here.

The reboot just made network-manager and iwd play more nicely; but wasn't this topic about wpa_supplicant NOT working, and replacing wpa_supplicant with iwd, but being aware of 'issues'?

So key-mgmt errors was not what I saw, but authentication was failling ...

but what you say with regards to `wext` is interesting; so that bit could be where things do get different. I'll try some ubuntu or mint or something to see if wext gets used there as well. I do still wonder what changed of course, as everything worked for a little over a decade.

Last edited by olliv3r (2024-12-20 18:23:00)

seth · 2024-12-20 20:25:12

iwd is being used as the network-manager backend; but nm keeps iwd running of course, and connecting the nwcli to the running daemon is/should be fine?

Yes. What you can not reliably do is bypass NM w/ using iwctl directly.

but wasn't this topic about wpa_supplicant NOT working, and replacing wpa_supplicant with iwd

The thread is about "NetworkManager 802-11-wireless-security.key-mgmt: property is missing." and that's the critical error.
There might be some stray posts about "my wifi doesn't work" that don't actually fit that pattern

So key-mgmt errors was not what I saw, but authentication was failling ...

More specifically

dec 14 18:38:36 2of9 NetworkManager[682]: <warn>  [1734197916.0340] device (wlp3s0): Activation: (wifi) association took too long
dec 14 18:38:36 2of9 wpa_supplicant[759]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=14:cc:20:8a:1a:c9 reason=3 locally_generated=1
…
wlp3s0: Authentication with 12:34 timed out.

I do still wonder what changed of course, as everything worked for a little over a decade.

Did you test the LTS kernel?
What kind of wifi chip/driver do you use?

Arch Linux

#1 2024-10-17 18:02:29

NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#2 2024-10-19 20:43:55

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#3 2024-10-21 11:04:48

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#4 2024-10-23 17:24:33

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#5 2024-11-07 21:54:39

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#6 2024-11-13 07:29:26

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#7 2024-11-13 15:02:13

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#8 2024-11-17 13:00:15

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#9 2024-11-17 14:20:31

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#10 2024-12-11 15:45:42

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#11 2024-12-12 12:34:05

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#12 2024-12-12 12:47:55

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#13 2024-12-12 20:13:01

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#14 2024-12-13 19:27:23

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#15 2024-12-13 22:02:41

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#16 2024-12-15 18:17:20

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#17 2024-12-15 20:13:05

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#18 2024-12-18 11:10:02

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#19 2024-12-18 13:57:50

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#20 2024-12-18 21:30:09

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#21 2024-12-18 21:48:06

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#22 2024-12-20 11:48:16

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#23 2024-12-20 14:40:43

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#24 2024-12-20 18:18:32

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

#25 2024-12-20 20:25:12

Re: NetworkManager 802-11-wireless-security.key-mgmt: property is missing.

Board footer