Network Manager still broken on my laptops

English Network/Internet
1

After an upgrade about a week ago I lost wifi connections and had to switch to Wicked to be able to connect my laptops and go on working.

My preferred configuration for our machines is for lan connected machines to be on Wicked and laptop connections on Network Manager (NM) as this is easier for roaming between SSIDs. The laptops are all on TW with KDE desktops.

Last night and since there have been many upgrades during the intervening period I tried to switch back to NM but to no avail, so am back on Wicked.

Not yet a problem but is this an unfixed bug or do I need to correct something in my system settings?

What tools do I use to investigate please?

Budge.

2

My system:

openSUSE Tumbleweed 20220206
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.4-1-default (64-bit)
Graphics Platform: X11

shows no problem when using NetworkManager.

Use YaST to switch your system from wicked to NetworkManager and then reboot your system (just to avoid unwanted left-overs). Execute

systemctl status network

if that shows no errors try to establish a network connection. Then do (as “root”)

journalctl -b 0 -t NetworkManager

and show the results of both commands.

Regards

susejunky

3

Easier said than done. Having switched to NM as suggested I have no internet connection so it is difficult to send you the info but with the command

systemctl status network

I had no errors shown but when I tried to connect to wifi I kept getting repeat attempts with requests for root pw and SSID pw one after another.

I ran the command you then suggested

have copied a few lines of the command you suggested:-

journalctl -b 0 -t NetworkManager

and saved it to a file. Having then switched back to Wicked I shall try and get it to you with susepaste.

Try this please:-
https://susepaste.org/22452699
Hope it works.

Or this:-
https://susepaste.org/20920794

4

Please run the command, capture output to a text file on a USB stick, and share here via an internet connected host.

5

Are you sure you supplied the correct values?

Regards

susejunky

6

Hi susejunky,
Difficult to be sure but I have done what I have always done and never had any issues like this before. I frequently have to move from one SSID/subnet and another and use NM all the time.

I have switched to NM again on this laptop, run the commands and recorded output to USB stick. Now I have switched back to Wicked so I can send these outputs and these are below:-

alastair@IBMT530:~> systemctl status network
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Thu 2022-02-10 18:24:03 GMT; 3min 35s ago
       Docs: man:NetworkManager(8)
   Main PID: 1289 (NetworkManager)
      Tasks: 3 (limit: 4915)
        CPU: 916ms
     CGroup: /system.slice/NetworkManager.service
             └─1289 /usr/sbin/NetworkManager --no-daemon

Warning: some journal files were not opened due to insufficient permissions.
alastair@IBMT530:~>

And the second command:-

alastair@IBMT530:~> sudo journalctl -b 0 -t NetworkManager
Feb 10 18:24:03 IBMT530 NetworkManager[1289]: <info>  [1644517443.8634] NetworkManager (version 1.32.12) is starting... (for the first time)
Feb 10 18:24:03 IBMT530 NetworkManager[1289]: <info>  [1644517443.8634] Read config: /etc/NetworkManager/NetworkManager.conf
Feb 10 18:24:03 IBMT530 NetworkManager[1289]: <info>  [1644517443.8655] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Feb 10 18:24:03 IBMT530 NetworkManager[1289]: <info>  [1644517443.8680] manager[0x55711edff000]: monitoring kernel firmware directory '/lib/firmware'.
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0395] hostname: hostname: using hostnamed
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0395] hostname: hostname changed from (none) to "IBMT530"
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0399] dns-mgr[0x55711ede1220]: init: dns=default,systemd-resolved rc-manager=netconfig
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0405] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80>
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0407] manager[0x55711edff000]: rfkill: Wi-Fi hardware radio set enabled
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0408] manager[0x55711edff000]: rfkill: WWAN hardware radio set enabled
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0439] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-adsl.so)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0488] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-blueto>
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0508] Loaded device plugin: NMOvsFactory (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-ovs.so)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0540] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-team.so)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0562] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-wifi.so)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0569] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-wwan.so)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0573] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0574] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0575] manager: Networking is enabled by state file
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0579] dhcp-init: Using DHCP client 'dhclient'
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0583] settings: Loaded settings plugin: keyfile (internal)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0668] device (lo): carrier: link connected
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0672] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0682] manager: (enp0s25): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.0693] device (enp0s25): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'exte>
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.2965] device (wlp3s0): driver supports Access Point (AP) mode
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.2971] manager: (wlp3s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.2978] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'exter>
Feb 10 18:24:04 IBMT530 NetworkManager[1289]: <info>  [1644517444.7077] device (wlp3s0): set-hw-addr: set MAC address to 42:67:B8:5F:90:6B (scanning)
Feb 10 18:24:05 IBMT530 NetworkManager[1289]: <info>  [1644517445.1093] ovsdb: Could not connect: No such file or directory
Feb 10 18:24:05 IBMT530 NetworkManager[1289]: <info>  [1644517445.1094] ovsdb: disconnected from ovsdb
Feb 10 18:24:05 IBMT530 NetworkManager[1289]: <info>  [1644517445.1150] modem-manager: ModemManager available
Feb 10 18:24:05 IBMT530 NetworkManager[1289]: <info>  [1644517445.2471] device (wlp3s0): supplicant interface state: internal-starting -> disconnected
Feb 10 18:24:05 IBMT530 NetworkManager[1289]: <info>  [1644517445.2472] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-ifa>
Feb 10 18:24:05 IBMT530 NetworkManager[1289]: <warn>  [1644517445.2478] device (wlp3s0): wifi-scan: active scanning for networks due to profiles with wifi.hidden=yes. Thi>
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.4270] policy: auto-activating connection 'wlp3s0' (835166ef-2ff2-4770-bdd9-0befcf510a15)
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.4281] device (wlp3s0): Activation: starting connection 'wlp3s0' (835166ef-2ff2-4770-bdd9-0befcf510a15)
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.4283] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.4288] manager: NetworkManager state is now CONNECTING
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.4428] device (wlp3s0): set-hw-addr: reset MAC address to 60:67:20:75:A4:72 (preserve)
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8509] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8517] device (wlp3s0): Activation: (wifi) access point 'wlp3s0' has security, but secrets are required.
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8518] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8525] device (wlp3s0): supplicant interface state: disconnected -> interface_disabled
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8543] device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8547] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8552] device (wlp3s0): Activation: (wifi) connection 'wlp3s0' has security, and secrets exist.  No new s>
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8553] Config: added 'ssid' value 'Private'
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8553] Config: added 'scan_ssid' value '1'
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8554] Config: added 'bgscan' value 'simple:30:-70:86400'
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8554] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE'
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8554] Config: added 'auth_alg' value 'OPEN'
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8554] Config: added 'psk' value '<hidden>'
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8681] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Feb 10 18:24:08 IBMT530 NetworkManager[1289]: <info>  [1644517448.8929] device (wlp3s0): supplicant interface state: inactive -> authenticating

alastair@IBMT530:~>

Hope this helps.

7

NetworkManager ist up and running so that is OK.

Please show the result of

sudo systemctl status network

and the content of the connection file (located /etc/NetworkManager/system-connections) which defines the connection which you are trying to establish.

Beware! If the connection file contains your network password remove it in your post.

Regards

susejunky

8

Here are the results of your commands strung together on USB as I switched between NM for test and back to Wicked for connection.
I didn’t see any passwords but please let me know if I am exposed as I shall have to change them.

alastair@IBMT530:~> systemctl status network
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Fri 2022-02-11 18:11:53 GMT; 2min 49s ago
       Docs: man:NetworkManager(8)
   Main PID: 5998 (NetworkManager)
      Tasks: 3 (limit: 4915)
        CPU: 836ms
     CGroup: /system.slice/NetworkManager.service
             └─5998 /usr/sbin/NetworkManager --no-daemon
alastair@IBMT530:~> sudo systemctl status network
[sudo] password for root: 
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Fri 2022-02-11 18:11:53 GMT; 3min 36s ago
       Docs: man:NetworkManager(8)
   Main PID: 5998 (NetworkManager)
      Tasks: 3 (limit: 4915)
        CPU: 896ms
     CGroup: /system.slice/NetworkManager.service
             └─5998 /usr/sbin/NetworkManager --no-daemon

Feb 11 18:14:08 IBMT530 NetworkManager[5998]: <warn>  [1644603248.1067] device (wlp3s0): Activation: (wifi) asso>
Feb 11 18:14:08 IBMT530 NetworkManager[5998]: <info>  [1644603248.1068] device (wlp3s0): state change: config ->>
Feb 11 18:14:08 IBMT530 NetworkManager[5998]: <info>  [1644603248.1074] manager: NetworkManager state is now DIS>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.5201] device (wlp3s0): set-hw-addr: set MAC ad>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <warn>  [1644603249.9197] device (wlp3s0): Activation: failed for >
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9200] device (wlp3s0): supplicant interface st>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9205] device (wlp3s0): supplicant interface st>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9209] device (wlp3s0): state change: failed ->>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9217] manager: startup complete
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9643] device (wlp3s0): supplicant interface st>
...skipping...
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Fri 2022-02-11 18:11:53 GMT; 3min 36s ago
       Docs: man:NetworkManager(8)
   Main PID: 5998 (NetworkManager)
      Tasks: 3 (limit: 4915)
        CPU: 896ms
     CGroup: /system.slice/NetworkManager.service
             └─5998 /usr/sbin/NetworkManager --no-daemon

Feb 11 18:14:08 IBMT530 NetworkManager[5998]: <warn>  [1644603248.1067] device (wlp3s0): Activation: (wifi) asso>
Feb 11 18:14:08 IBMT530 NetworkManager[5998]: <info>  [1644603248.1068] device (wlp3s0): state change: config ->>
Feb 11 18:14:08 IBMT530 NetworkManager[5998]: <info>  [1644603248.1074] manager: NetworkManager state is now DIS>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.5201] device (wlp3s0): set-hw-addr: set MAC ad>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <warn>  [1644603249.9197] device (wlp3s0): Activation: failed for >
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9200] device (wlp3s0): supplicant interface st>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9205] device (wlp3s0): supplicant interface st>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9209] device (wlp3s0): state change: failed ->>
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9217] manager: startup complete
Feb 11 18:14:09 IBMT530 NetworkManager[5998]: <info>  [1644603249.9643] device (wlp3s0): supplicant interface st>
~
~

alastair@IBMT530:~> cd /etc/NetworkManager/system-connections
alastair@IBMT530:/etc/NetworkManager/system-connections> ls
Bex Private BT A_C.nmconnection
dd-wrt.nmconnection
DHCP connection.nmconnection
enp0s25.nmconnection
Errichel_Guests.nmconnection
ipvanish-DE-Frankfurt-fra-a30.nmconnection
ipvanish-DE-Frankfurt-fra-a37.nmconnection
ipvanish-NL-Amsterdam-ams-a21.nmconnection
ipvanish-NL-Amsterdam-ams-a50.nmconnection
New 802-11-wireless connection-7bd77246-bcba-4314-8f08-8e5f56ae27d2.nmconnection
New 802-11-wireless connection.nmconnection
New 802-3-ethernet connection-7ecfae3e-5eb8-42c0-8f0b-b1791cf7338b.nmconnection
New 802-3-ethernet connection.nmconnection
Private.nmconnection
Wired connection 1.nmconnection
alastair@IBMT530:/etc/NetworkManager/system-connections>

Hope this helps and thanks for your help.
Budge

9

Nice to see that you have quite a few connections set up.

But didn’t i ask you to show the content of the .nmconnection-file which belongs to the connection that you tried to establish without success?

Regards

susejunky

10

Sorry, I missed that but which should I show. The connection I want to work is the wifi to hidden SSID “Private.”
I hope this is OK and I have obscured the pw.:-

alastair@IBMT530:/etc/NetworkManager/system-connections> sudo cat Private.nmconnection 
[sudo] password for root:  
[connection] 
id=wlp3s0 
uuid=835166ef-2ff2-4770-bdd9-0befcf510a15 
type=wifi 
interface-name=wlp3s0 
permissions= 
zone=work 

[wifi] 
hidden=true 
mac-address=60:67:20:75:A4:72 
mac-address-blacklist= 
mode=infrastructure 
ssid=Private 

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

[ipv4] 
dns-search= 
may-fail=false 
method=auto 

[ipv6] 
addr-gen-mode=stable-privacy 
dns-search= 
method=auto 

[proxy] 
alastair@IBMT530:/etc/NetworkManager/system-connections>

Is this any help?

11

This connection will only connect to MAC-address=60:67:20:75:A4:72.

Are you sure that SSID “Private” is provided by a wifi-router with this MAC-address?

The NetworkManager documentation says

|auth-alg| When WEP is used (ie, key-mgmt = “none” or “ieee8021x”) indicate the 802.11 authentication algorithm required by the AP here. One of “open” for Open System, “shared” for Shared Key, or “leap” for Cisco LEAP. When using Cisco LEAP (ie, key-mgmt = “ieee8021x” and auth-alg = “leap”) the “leap-username” and “leap-password” properties must be specified.
|—|
Format: string|

so i think that “auth-alg=open” does not fit with “key-mgmt=wpa-psk”.

Regards

susejunky

12

Hi susejunky,
Interesting but I have no idea how the MAC address you quote was obtained but this is the MAC address on my wifi NIC on my system as evidenced by this command:-

3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 
    link/ether 60:67:20:75:a4:72 brd ff:ff:ff:ff:ff:ff 
    inet 192.168.169.164/25 brd 192.168.169.255 scope global wlp3s0 
       valid_lft forever preferred_lft forever 
alastair@IBMT530:~>

.
These laptops roam our site and use one of half a dozen APs depending on location within the site.
These APs are configured with several SSIDs, usually 3, some hidden and some visible.
Each SSID connects to a different subnet and serves a different purpose but clearly the same SSID is used for the same subnet on all devices.
The network is managed using vlans and managed switches switches.
Depending on task in hand I may need to connect to different SSIDs to access the required subnet.
I do this frequently every week.
Whatever has caused my present problem is not through anything I have done intentionally and I am not aware what has changed.
I shall look again at my settings and see if there is something missing.
Thanks for the help.
Regards,
Budge.

13

I have checked the WiFi AP firmware and all devices are up to date.

The problem is clearly due to recent changes in TW and I cannot connect with either WPA-PSK private version 2 or version 3.

Most of the APs are set for WPA2/WPA3-personal which has been the case for over a year and I regret to inform everybody that Windoze has not had any difficulty connecting from the same laptops.

What I don’t understand is why nobody else has this problem. Thank goodness Wicked is still working well.
Budge

14

This evening I ran zypper dup to upgrade and after a reboot I tried NM again and it is now working.
I am glad but it would have been good to understand what had been broken by the earlier uograde.

15

Hmm … you could be affected by 1195395 – hardware/wpa_supplicant: Not able to connect to WLAN after wpa_supplicant update to version 2.10

Unfortunately you artificially restricted logs to NetworkManager only, so we do not know if wpa_suplicant messages look similar.

16

Hi arvidjaar,
Thanks for the help. Sorry I artificially restricted logs but I only supplied what was requested and have no idea what I should have done. Just glad it has been resolved or seems to have been today. Now I can get back to work!
Many thanks,
Budge.

17

It is most likely wpa_supplicant update. Which shows that it is important to have full logs from all components in stack.