WiFi connection not working on startup for some networks

LinG · 2018-03-30 11:44:23

Hello,

When I first set up my system the Wifi to my home network would automatically connect on startup. However, a few months back the first time connecting on startup wouldn't work. It would heavily tax my CPU but it would never succeed to connect. So I would have to manually disconnect and connect in order to establish a Wifi connection. So that's a bit annoying but since it's only once every time I start my system up, I was willing to deal with that (until I found a better solution).

Now recently I started to work somewhere else and bring my personal laptop. At work, however, my laptop would connect to the wifi on startup fine without any issues. So apparently it can work, so I wanted to achieve a flawless wifi connection at my Wifi network at home as well on startup.

I thought that it might have to do with some settings that got messed up so I used

nmcli con

to list the uuid and

nmcli con delete uuid *insert id*

to delete my home networks.

but after connecting with them again and a reboot I still had the same problem. I also tried to remove NetworkManager completely and then install it again but that didn't help either...

So, I come here to ask if someone has an idea what the issue might be (that I am able to connect to my wifi at work fine but that my wifi at home does not) and give me some pointers in the right direction, thank you very much in advance.

Installed:

plasma
networkmanager
networkmanager-qt
plasma-nm

journal:

Mar 29 09:23:52 Arch-PC kdeinit5[471]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "AllDevices"
Mar 29 09:23:52 Arch-PC kdeinit5[471]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "Capabilities"
Mar 29 09:23:52 Arch-PC kdeinit5[471]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "ConnectivityCheckAvailable"
Mar 29 09:23:52 Arch-PC kdeinit5[471]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "ConnectivityCheckEnabled"
Mar 29 09:23:52 Arch-PC kdeinit5[471]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "Devices"
Mar 29 09:23:52 Arch-PC kdeinit5[471]: networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "GlobalDnsConfiguration"

Last edited by LinG (2018-03-30 11:48:15)

seth · 2018-03-30 11:51:51

The journal entries for your NM GUI are rather useless, it's NM that actually handles your network.
Speaking of which:
a) ensure you do not have any other network managing services enabled
b) stop NM and try a https://wiki.archlinux.org/index.php/Wi … nual_setup

LinG · 2018-03-30 15:07:11

seth wrote:

The journal entries for your NM GUI are rather useless, it's NM that actually handles your network.
Speaking of which:
a) ensure you do not have any other network managing services enabled
b) stop NM and try a https://wiki.archlinux.org/index.php/Wi … nual_setup

yes my bad, after a little digging I found the ones by NetworkManager itself

 Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6859] policy: auto-activating connection 'Thuis_12'
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6873] device (wlp2s0): Activation: starting connection 'Thuis_12' (6210e4ca-e3c5-4af1-ba02-b7f209ccc05d)
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6875] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6877] manager: NetworkManager state is now CONNECTING
Mar 30 16:57:46 Arch-PC systemd[1]: Starting User Manager for UID 1000...
Mar 30 16:57:46 Arch-PC systemd-logind[297]: New session c2 of user ling.
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6903] device (wlp2s0): set-hw-addr: reset MAC address to A0:C5:89:2D:20:D0 (preserve)
Mar 30 16:57:46 Arch-PC systemd[1]: Started Session c2 of user ling.
Mar 30 16:57:46 Arch-PC systemd[426]: pam_unix(systemd-user:session): session opened for user ling by (uid=0)
Mar 30 16:57:46 Arch-PC kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6953] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6955] device (wlp2s0): Activation: (wifi) access point 'Thuis_12' has security, but secrets are required.
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6955] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.6956] sup-iface[0x5639b6e9c220,wlp2s0]: wps: type pbc start...
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <warn>  [1522421866.7029] device (wlp2s0): No agents were available for this request.
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.7109] device (wlp2s0): supplicant interface state: ready -> disconnected
Mar 30 16:57:46 Arch-PC NetworkManager[296]: <info>  [1522421866.7121] device (wlp2s0): supplicant interface state: disconnected -> inactive

I suppose it's the warning about "no agents were available for this request", that's the problem?

a) Did that I seem to have netctl and NetworkManager installed but I could only find NetworkManager.service in systemctl (using a quick grep), so I think that's fine...
b) I am able to connect fine manually to the network, I just want my system to connect on startup automatically.

robg · 2018-03-30 16:58:10

LinG wrote:

I am able to connect fine manually to the network, I just want my system to connect on startup automatically.

To further isolate the impact of NetworkManager, does connecting via netctl (https://wiki.archlinux.org/index.php/Netctl) work? If so, does autoconnect via netctl-auto.service also work?

seth · 2018-03-30 17:48:35

LinG wrote:

I suppose it's the warning about "no agents were available for this request", that's the problem?

You need a polkit agent, is https://www.archlinux.org/packages/extr … kde-agent/ not running?

Arch Linux

#1 2018-03-30 11:44:23

WiFi connection not working on startup for some networks

#2 2018-03-30 11:51:51

Re: WiFi connection not working on startup for some networks

#3 2018-03-30 15:07:11

Re: WiFi connection not working on startup for some networks

#4 2018-03-30 16:58:10

Re: WiFi connection not working on startup for some networks

#5 2018-03-30 17:48:35

Re: WiFi connection not working on startup for some networks

Board footer