Tumbleweed Network Manager fails to reconnect

Hi all,

Recently my network manager becomes unstable. It connects fine upon first system boot, then after a while disconnects and fails to auto connect. Even if I try to reconnect manually, it always reports no passwords given and no authentication agent is available.

I ran journactl and try connect, and saw the following logs:

lynxiayel@alienware:~>sudo journalctl -fu NetworkManager
[sudo] password for root:  
-- Logs begin at Fri 2016-11-11 12:48:12 CST. --
Sep 12 13:43:38 alienware.OpenSUSE dhclient[14195]: receive_packet failed on wlan0: Network is down
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731018.2992] device (wlan0): set-hw-addr: reset MAC address to 54:35:30:8A:42:E1 (preserve)
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <warn>  [1536731018.3093] sup-iface[0x55c087d8d8d0,wlan0]: connection disconnected (reason -3)
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731018.3148] device (wlan0): supplicant interface state: completed -> disabled
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731018.3151] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731018.3154] device (wlan0): Activation: (wifi) access point 'CGRAchen' has security, but secrets are required.
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731018.3154] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731018.3156] sup-iface[0x55c087d8d8d0,wlan0]: wps: type pbc start...
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <warn>  [1536731018.3162] device (wlan0): No agents were available for this request.
Sep 12 13:43:38 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731018.3378] device (wlan0): supplicant interface state: disabled -> scanning
Sep 12 13:44:08 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731048.2242] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Sep 12 13:44:08 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731048.2248] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 12 13:44:08 alienware.OpenSUSE NetworkManager[14629]: <warn>  [1536731048.2255] device (wlan0): Activation: failed for connection 'CGRAchen'
Sep 12 13:44:08 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731048.2259] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 12 13:44:08 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731048.2418] device (wlan0): set-hw-addr: set MAC address to 8E:88:33:9B:0A:89 (scanning)
Sep 12 13:44:08 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731048.2568] device (wlan0): supplicant interface state: scanning -> disabled
Sep 12 13:44:08 alienware.OpenSUSE dhclient[14195]: receive_packet failed on wlan0: Network is down
Sep 12 13:44:08 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731048.2698] device (wlan0): supplicant interface state: disabled -> scanning
Sep 12 13:44:11 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731051.6712] device (wlan0): supplicant interface state: scanning -> disconnected
Sep 12 13:44:15 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731055.0774] device (wlan0): supplicant interface state: disconnected -> authenticating
Sep 12 13:44:15 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731055.0848] device (wlan0): supplicant interface state: authenticating -> associating
Sep 12 13:44:15 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731055.0911] device (wlan0): supplicant interface state: associating -> associated
Sep 12 13:44:15 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731055.2063] device (wlan0): supplicant interface state: associated -> 4-way handshake
Sep 12 13:44:15 alienware.OpenSUSE NetworkManager[14629]: <info>  [1536731055.2137] device (wlan0): supplicant interface state: 4-way handshake -> completed

I am running tumbleweed with kernel Linux 4.18.5-1-default, and KDE 5.49.0 / Plasma 5.13.4, any ideas what’s the problem? Thanks in advance.

Default question re. Tw: How did you upgrade Tw?
If through some applet or YaST, don’t, Tw only supports ‘zypper dup’ due to it’s nature.

Your log says that your configured network connection is not providing your connection password.

Either your Network Manager is faulty or your network connection configuration is faulty.
Recommend looking at your network connection configuration first.

TSU

I’m updating with

zypper dup --no-allow-vendor-change

If you mean the settings for each connection in Network Manager, it’s just the old same, saved passwords, connect automatically being checked etc.
As for the NetworkManager itself, is there a configuration file? Sorry I googled around and don’t seem to find one.

I meant just the connection setting, not NM itself so you say you’ve done that.

I’d personally recommend upgrading allowing a vendor change.
If you find it causes a problem and you’re installed on BTRFS you have the option to roll back.

Maybe try connecting manually (not on system boot) for awhile to see if you still see the problem.
If you don’t see a problem, then switch back to connecting on system boot again.
If you don’t see more clues in logs or by circumstantial evidence, there’s a lot to look at, IMO

  • Whether your password is stored in kwallet or not
  • Whether your password is being written to wpa_supplicant.conf

TSU

When using NM and the connection is configred as a “system connection”, the credentials are stored in the NetworkManager connection profile itself.

Which would be another place to look if NM stores its connection profiles differently than when I looked before.
When I was studying NM a few years ago, the “connection profile” was stored in the standard wpa_supplicant.conf, sometimes as a hash and other times as plain text.
And, at the time this always the case whether the password was also stored in another place like kwallet.

TSU