You are not logged in.

#1 2020-07-26 22:41:34

m4ttj
Member
Registered: 2020-07-26
Posts: 3

[SOLVED] NetworkManager needs restarting on boot with IWD

Hi, I'm using NetworkManager with IWD as the backend and systemd to start.

On boot NetworkManager reports the wifi interface to be unavailable and I can't connect with nmcli or the KDE applet and need to restart the NetworkManager unit each time at boot for it to start working.

Running

journalctl -u NetworkManager -b
Jul 26 23:19:28 laptop systemd[1]: Starting Network Manager...
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.2523] NetworkManager (version 1.26.0-1) is starting... (for the first time)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.2524] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Jul 26 23:19:28 laptop systemd[1]: Started Network Manager.
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.2559] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.2618] manager[0x55d995eec0c0]: monitoring kernel firmware directory '/lib/firmware'.
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.7765] hostname: hostname: using hostnamed
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.7766] hostname: hostname changed from (none) to "laptop"
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.7770] dns-mgr[0x55d995ecb220]: init: dns=default,systemd-resolved rc-manager=symlink
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.7777] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill0) (d>
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.7778] manager[0x55d995eec0c0]: rfkill: Wi-Fi hardware radio set enabled
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.7778] manager[0x55d995eec0c0]: rfkill: WWAN hardware radio set enabled
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.7891] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.26.0-1/libnm-device-plugin-bluetooth.so)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8008] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.26.0-1/libnm-device-plugin-team.so)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8018] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.26.0-1/libnm-device-plugin-ovs.so)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8035] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.26.0-1/libnm-device-plugin-wifi.so)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8043] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.26.0-1/libnm-device-plugin-adsl.so)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8048] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.26.0-1/libnm-device-plugin-wwan.so)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8052] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8053] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8054] manager: Networking is enabled by state file
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8061] dhcp-init: Using DHCP client 'internal'
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8072] settings: Loaded settings plugin: keyfile (internal)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8142] device (lo): carrier: link connected
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8145] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8155] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/2)
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8202] ovsdb: Could not connect: No such file or directory
Jul 26 23:19:28 laptop NetworkManager[550]: <info>  [1595801968.8216] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 26 23:19:29 laptop NetworkManager[550]: <info>  [1595801969.0601] manager: startup complete
Jul 26 23:19:40 laptop NetworkManager[550]: <info>  [1595801980.6383] agent-manager: agent[9abd9452b7c11dcb,:1.32/org.kde.plasma.networkmanagement/1000]: agent registered
Jul 26 23:19:43 laptop NetworkManager[550]: <info>  [1595801983.6178] manager: (RA:ND:OM:12:34:56): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/3)
Jul 26 23:19:43 laptop NetworkManager[550]: <info>  [1595801983.6206] device (RA:ND:OM:12:34:56): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 26 23:19:43 laptop NetworkManager[550]: <info>  [1595801983.6262] device (RA:ND:OM:12:34:56): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')

and

journalctl -u iwd -b
Jul 26 23:19:28 laptop systemd[1]: Starting Wireless service...
Jul 26 23:19:29 laptop iwd[722]: Wireless daemon version 1.8
Jul 26 23:19:29 laptop iwd[722]: Loaded configuration from /etc/iwd/main.conf
Jul 26 23:19:29 laptop systemd[1]: Started Wireless service.
Jul 26 23:19:29 laptop iwd[722]: station: Network configuration is disabled.
Jul 26 23:19:29 laptop iwd[722]: Wiphy: 0, Name: phy0
Jul 26 23:19:29 laptop iwd[722]:         Permanent Address: ra:nd:om:12:34:56
Jul 26 23:19:29 laptop iwd[722]:         Bands: 2.4 GHz 5 GHz
Jul 26 23:19:29 laptop iwd[722]:         Ciphers: CCMP TKIP BIP
Jul 26 23:19:29 laptop iwd[722]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Jul 26 23:19:29 laptop iwd[722]: Wiphy phy0 will only use the default interface
Jul 26 23:24:04 laptop iwd[722]: Received Deauthentication event, reason: 3, from_ap: false

Really not sure why it's not working, I've looked at the wiki and can't seem to find anything relevant. It was working for a long while but seems to have broke at some point so any help would be appreciated? Thanks.

Last edited by m4ttj (2020-07-27 12:19:19)

Offline

#2 2020-07-26 22:48:36

GaKu999
Member
Registered: 2020-06-21
Posts: 124

Re: [SOLVED] NetworkManager needs restarting on boot with IWD

That’s expected since NetworkManager IWD support is still an experimental WIP...

You can view more detailed info in the wiki here.

There’s an open issue at their repository regarding this:
https://gitlab.freedesktop.org/NetworkM … issues/101

You may track it’s progress until it’s solved.

I recommend that unless you have a specific reason to use IWD as the NM backend you use instead the default wpa_supplicant...

Last edited by GaKu999 (2020-07-26 22:54:07)

Offline

#3 2020-07-26 23:10:50

m4ttj
Member
Registered: 2020-07-26
Posts: 3

Re: [SOLVED] NetworkManager needs restarting on boot with IWD

Ah right, was well aware it's WIP, probably should've checked the git repo. I'm not running networkmanager-iwd from the AUR, just normal extra/networkmanager and it has been working perfectly fine until I had this issue; as far as I can tell all networkmanager-iwd does is set iwd as the default backend thus allowing the wpa_supplicant dependency to be removed (I'm not too fussed by this).

I'll admit I have no particular reason for using iwd other than the significant connection speed improvements it gave me (like 7 seconds on boot and 4 on system resume) but I don't mind dealing with some issues.

In the repo starting iwd with systemd was suggested (and works for me) is there any reason to not do this and leave it up to NetworkManager to start iwd?

Last edited by m4ttj (2020-07-26 23:13:03)

Offline

#4 2020-07-26 23:19:29

GaKu999
Member
Registered: 2020-06-21
Posts: 124

Re: [SOLVED] NetworkManager needs restarting on boot with IWD

m4ttj wrote:

In the repo starting iwd with systemd was suggested (and works for me) is there any reason to not do this and leave it up to NetworkManager to start iwd?

I don’t think NM can’t start IWD...you may test if it does but I doubt so...

About the speed issues in other threads it was found that it’s because of the module loading logic...if you are well versed in that you may search which modules you hardware needs that are loaded by IWD but missed by wpa_supplicant.

Once you find them, loading those modules makes any network managing setup equal...at least that was the result of the initial experimentation...

Offline

Board footer

Powered by FluxBB