I’m staying at other person’s house and yesterday the wifi network worked until it didn’t.
Suddenly the connection dropped and when I’m trying to reconnect it shows a message “Authorization supplicant failed” and the connection drops.
I cannot verify whether this happens with other networks, as I don’t have access to any other network.
I’ve tried googling, but no success. Tried restarting system, restarting NetworkManager service.
I haven’t seen your problem before,
But when I do a search on your error (assuming your error is recounted accurately)
I see at least the following two fixes for other people.
Modify your network card configuration’s powersave option. I don’t know how much sense this makes.
https://unix.stackexchange.com/questions/585063/wireless-interface-authorization-supplicant-failed-kubuntu-20-04
Modify your netowrk card configuration’s support for 802.11n (disable) This makes some sense to me but it’s too bad if it has to be disabled
https://www.linuxquestions.org/questions/slackware-14/networkmanager-fails-to-connect-authentication-problem-4175535006/
You might want to see if you can gather better information, maybe more descriptive details might be written to your system log.
You can search your log for the error or you can display your system events in real time by opening a command line console, run the following command and leave it open. When your system disconnects, see if anything informative is displayed, and what might have preceded the disconnection. Maybe when you fail to reconnect you’ll get something interesting at that time, too.
journalctl -f
HTH,
TSU
Well, I’ve seen the pages you posted and none of the “fixes” I found worked for me and ie. the first one you linked doesn’t seem to be available for oS at all, since the file is missing.
And somehow I solved the problem by removing the <network_name>.nmconnection file from /etc/NetworkManger/system-connections. I don’t know what this did, but after the reboot wifi connected like it should.
Out of curiosity I compared the file I deleted and the new one that was created and in the fragment:
[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk-flags=1
in the old one “auth-alg=open” was missing.
I also looked at the system log like you suggested and I think the interesting event is:
21:45:40 thinker NetworkManager[1355]: <warn> [1598384740.6820] sup-iface[0x55fe15282310,wlan0]: assoc[0x55fe152da100]: failure to add network: invalid message format
But googling it gave me nothing that I could use. Perhaps I didn’t look enough.
Anyway, somehow I managed to fix it for now. Just posting this because I thought it might be useful for someone if they encounter similar problem.
Congrats on finding your problem.
In the links I posted, the discussions were careful to state that those solutions worked specifically for those network cards, not all network cards are guaranteed to set up the same (Every vendor has their own idea how things should work).
It does make a bit of sense that your solution has something to do with the authentication algorithm, but it’s unclear what the problem is. Somehow explicitly specifying “open” in your case seems to loosen restrictions, but I wonder in what way and if has something to do with re-authenticating could expose you to a MIM attack. But, of course if your WiFi isn’t in the middle of a congested office area, I’d say physical attempts to hack you would be fairly slim.
This is the little bit of info I found…
I’m not sure, but I think that in this context “open system” is the setting for access without password which would be a WiFi public hot spot without password.
If that’s the case… then I suspect that your client somehow believes that no password should be sent to the AP on re-connection.
https://developer.gnome.org/NetworkManager/stable/settings-802-11-wireless-security.html
You didn’t post the manufacturer and model of the AP you’re connecting to, maybe there is something specific to that hardware.
TSU
I just ran into this in a hotel with OWE passwordless wifi, and none of the above suggestions worked - kept getting the “failure to add network: invalid message format” error from sup-iface:
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8521] device (wlp82s0): Activation: starting connection 'SLS 2' (d8bc4e24-88a3-4ec0-889c-9bca5d3dcc25)Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8521] device (wlp82s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8523] manager: NetworkManager state is now CONNECTING
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8539] device (wlp82s0): set-hw-addr: reset MAC address to 4C:1D:96:AF:EC:36 (preserve)
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8555] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8556] device (wlp82s0): Activation: (wifi) connection 'SLS 2' has security, and secrets exist. No new secrets needed.
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8556] Config: added 'ssid' value 'SLS'
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8556] Config: added 'scan_ssid' value '1'
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8556] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8556] Config: added 'key_mgmt' value 'OWE'
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8556] Config: added 'auth_alg' value 'OPEN'
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.8556] Config: added 'ieee80211w' value '2'
Jan 12 08:48:36 aegean NetworkManager[26136]: <warn> [1641977316.9239] sup-iface[ed49ddcdc9c51d2f,11,wlp82s0]: assoc[e9bebbd293150025]: failure to add network: invalid message format
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.9240] device (wlp82s0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed')
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.9241] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 12 08:48:36 aegean NetworkManager[26136]: <warn> [1641977316.9242] device (wlp82s0): Activation: failed for connection 'SLS 2'
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.9243] device (wlp82s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 12 08:48:36 aegean NetworkManager[26136]: <info> [1641977316.9260] device (wlp82s0): set-hw-addr: set MAC address to D2:B0:5C:A0:C3:D6 (scanning)
Every time I edited settings for the wifi network in nm-connection-editor and retried, it would create a new network with default settings by appending ’ 1’, ’ 2’ etc. to the end, effectively ignoring any setting changes I made. In the end I found that
nmcli c up 'SLS 2'
activated the existing network config straight away and the issue vanished. I have no idea why, but it seems like maybe it’s a bug with nm-applet. For example if I renamed the network display name in nm-connection-editor to something like ‘SLS test’ then clicking the icon in the system tray to see the list of available networks would still only display ‘SLS’ i.e. the original SSID rather than the NM network display name I configured. So if you had multiple networks with different configs for the same SSID (e.g. ‘SLS 2.4GHz’ and ‘SLS 5GHz’) then apparently nm-applet doesn’t let you choose between them and you have to use nmcli. All very strange and not a pleasant experience.
I think it will be better when you first upgrade to openSUSE 15.3 and then try to re-create your problem. Much easier to help with a problem on a supported version (because the helpers will use that also) and also, when a bug report might be needed, you can not file one against an End of Life version.