wpa_supplicant seems to require regular restarts with network manager

HenryJia · 2025-12-03 17:13:28

I have a little server in my university office which runs mostly headless using NetworkManager which I configured using nmcli.

I'm connecting it to the wifi using wpa_supplicant and dhcpcd in the backend based on the Arch Wiki

I've noticed that it seems to require me to restart wpa_supplicant.service once every 24 hours or so, or NetworkManager stops being able to communicate with it and winds up timing out trying out to use it.

Once I restart wpa_supplicant everything seems to work fine for another 24 hours or so.

I've done some digging through the Arch Wiki and I've not found anything similar in the troubleshooting sections

Any suggestions?

I could write a systemd-timer to just restart wpa_supplicant regularly, but that's somewhat of an inelegant solution

system72 · 2025-12-03 18:29:00

network manager has its own internal dhcp client, make sure network manager is configured to use dhcpcd if you truly want to use that

https://wiki.archlinux.org/title/Networ … HCP_client

V1del · 2025-12-03 19:23:43

you should not start wpa_supplicant at all when running nmcli and NetworkManager, networkmanager starts those automatically and correctly itself, you running it via the service at the "same" time will create a logical conflict, same for dhcpcd as mentioned earlier. What's your output for

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Last edited by V1del (2025-12-03 19:24:20)

HenryJia · 2025-12-05 18:17:47

This is what running that command yields

henry@mainstay ~ % find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
coolercontrold.service                   | multi-user.target.wants
dbus-org.freedesktop.nm-dispatcher.service | system
getty@tty1.service                       | getty.target.wants
haproxy.service                          | multi-user.target.wants
high-power.timer                         | timers.target.wants
lm_sensors.service                       | multi-user.target.wants
low-power.timer                          | timers.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
NetworkManager.service                   | multi-user.target.wants
nvidia-hibernate.service                 | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-suspend.service.wants
nvidia-suspend.service                   | systemd-suspend.service.wants
openvpn-client@central-iceland.service   | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-userdbd.socket                   | sockets.target.wants

I don't have dhcpcd or wpa_supplicant enabled. I'm aware that it causes conflicts. I configured NetworkManager to use dhcpcd (as per Archwiki) instead of its internal dhcp client because I found that NetworkManager's dhcp client didn't have very verbose logging. I wanted to rule out that it wasn't NetworkManager's black box dhcp client being weird.

It turns out there's something strange going on between NetworkManager and wpa_supplicant. wpa_supplicant isn't enabled and it seems like the service is being correctly started by NetworkManager

But, after about 18-24 hours, NetworkManager would then always lose the ability to communicate with it and time out whilst doing so. The only thing that would fix this is running

 systemctl stop wpa_supplicant

which causes NetworkManager to restart wpa_supplicant, which would then delay it by another 18-24 hours

This is the journalctl output from boot to when NetworkManager stops working

Dec 03 17:48:46 mainstay systemd[1]: Starting Network Manager...
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.7969] NetworkManager (version 1.54.2-1) is starting... (boot:4d4f98ff-5db1-48f7-b028-91760ab0e057)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.7972] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/20-connectivity.conf, /etc/NetworkManager/conf.d/{dhcp-client.conf,dns-servers.conf,wifi_rand_mac.conf}
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8041] manager[0x558fbdef8260]: monitoring kernel firmware directory '/lib/firmware'.
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8349] hostname: hostname: using hostnamed
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8349] hostname: static hostname changed from (none) to "mainstay"
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8352] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8363] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:0a:00.0/0000:0b:04.0/0000:0d:00.0/ieee80211/phy0/rfkill1) (driver mt7921e)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8364] manager[0x558fbdef8260]: rfkill: Wi-Fi hardware radio set enabled
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8364] manager[0x558fbdef8260]: rfkill: WWAN hardware radio set enabled
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8464] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.54.2-1/libnm-device-plugin-adsl.so)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8694] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.54.2-1/libnm-device-plugin-team.so)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8724] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.54.2-1/libnm-device-plugin-bluetooth.so)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8729] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.54.2-1/libnm-device-plugin-ovs.so)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8732] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.54.2-1/libnm-device-plugin-wwan.so)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8741] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.54.2-1/libnm-device-plugin-wifi.so)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8742] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8742] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8743] manager: Networking is enabled by state file
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8746] settings: Loaded settings plugin: keyfile (internal)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8791] dhcp: init: Using DHCP client 'dhcpcd'
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8793] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8797] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8799] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8803] device (lo): Activation: starting connection 'lo' (62e1afe8-13fb-42c1-9285-bb0758a9a43c)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8808] manager: (enp14s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8811] settings: (enp14s0): created default wired connection 'Wired connection 1'
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.8811] device (enp14s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.9930] device (wlp13s0): driver supports Access Point (AP) mode
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.9935] manager: (wlp13s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Dec 03 17:48:46 mainstay NetworkManager[633]: <info>  [1764784126.9935] device (wlp13s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5379] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Dec 03 17:48:47 mainstay systemd[1]: Started Network Manager.
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5387] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:14:00.0/usb3/3-5/3-5:1.0/ieee80211/phy1/rfkill2) (driver mt7921u)
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5403] ovsdb: disconnected from ovsdb
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5403] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5404] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5405] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5407] device (wlp20s0u5): driver supports Access Point (AP) mode
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5409] manager: (wlp20s0u5): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/4)
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5410] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5416] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Dec 03 17:48:47 mainstay NetworkManager[633]: <info>  [1764784127.5416] device (wlp20s0u5): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.1358] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.1447] device (lo): Activation: successful, device activated.
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2124] device (wlp13s0): supplicant interface state: internal-starting -> disconnected
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2124] Wi-Fi P2P device controlled by interface wlp13s0 created
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2125] manager: (p2p-dev-wlp13s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5)
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2126] device (p2p-dev-wlp13s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Dec 03 17:48:48 mainstay NetworkManager[633]: <warn>  [1764784128.2126] device (p2p-dev-wlp13s0): error setting IPv4 forwarding to '0': Resource temporarily unavailable
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2128] device (wlp20s0u5): supplicant interface state: internal-starting -> disconnected
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2128] Wi-Fi P2P device controlled by interface wlp20s0u5 created
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2129] manager: (p2p-dev-wlp20s0u5): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6)
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2129] device (p2p-dev-wlp20s0u5): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Dec 03 17:48:48 mainstay NetworkManager[633]: <warn>  [1764784128.2129] device (p2p-dev-wlp20s0u5): error setting IPv4 forwarding to '0': Resource temporarily unavailable
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2131] device (wlp13s0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2132] device (p2p-dev-wlp13s0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2133] device (wlp20s0u5): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Dec 03 17:48:48 mainstay NetworkManager[633]: <info>  [1764784128.2134] device (p2p-dev-wlp20s0u5): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4319] policy: auto-activating connection 'wlan1-eduroam' (49b56e77-24e6-4bbd-9d98-d62ae5ee2aa7)
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4320] policy: auto-activating connection 'wlan0-eduroam' (835e11ff-14be-4837-9742-3823080f237f)
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4321] device (wlp20s0u5): Activation: starting connection 'wlan1-eduroam' (49b56e77-24e6-4bbd-9d98-d62ae5ee2aa7)
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4322] device (wlp13s0): Activation: starting connection 'wlan0-eduroam' (835e11ff-14be-4837-9742-3823080f237f)
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4322] device (wlp20s0u5): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4323] manager: NetworkManager state is now CONNECTING
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4323] device (wlp20s0u5): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4325] device (wlp20s0u5): Activation: (wifi) access point 'wlan1-eduroam' has security, but secrets are required.
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4325] device (wlp20s0u5): state change: config -> need-auth (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4325] device (wlp13s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4326] device (wlp13s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4327] device (wlp13s0): Activation: (wifi) access point 'wlan0-eduroam' has security, but secrets are required.
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4327] device (wlp13s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4333] device (wlp20s0u5): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4334] device (wlp20s0u5): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] device (wlp20s0u5): Activation: (wifi) connection 'wlan1-eduroam' has security, and secrets exist.  No new secrets needed.
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] Config: added 'ssid' value 'eduroam'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] Config: added 'scan_ssid' value '1'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] Config: added 'bssid' value 'A4:00:4E:05:06:22'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] Config: added 'password' value '<hidden>'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] Config: added 'eap' value 'PEAP'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] Config: added 'fragment_size' value '1266'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4335] Config: added 'phase2' value 'auth=MSCHAPV2'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4386] Config: added 'identity' value 'u1705507@warwick.ac.uk'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4386] Config: added 'proactive_key_caching' value '1'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4387] device (wlp13s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4388] device (wlp13s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4389] device (wlp13s0): Activation: (wifi) connection 'wlan0-eduroam' has security, and secrets exist.  No new secrets needed.
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4389] Config: added 'ssid' value 'eduroam'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'scan_ssid' value '1'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'bssid' value 'A4:00:4E:05:06:2D'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'password' value '<hidden>'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'eap' value 'PEAP'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'fragment_size' value '1266'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'phase2' value 'auth=MSCHAPV2'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'identity' value 'u1705507@warwick.ac.uk'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.4390] Config: added 'proactive_key_caching' value '1'
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.5766] device (wlp20s0u5): supplicant interface state: disconnected -> authenticating
Dec 03 17:48:50 mainstay NetworkManager[633]: <info>  [1764784130.5766] device (p2p-dev-wlp20s0u5): supplicant management interface state: disconnected -> authenticating
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1150] device (wlp13s0): supplicant interface state: disconnected -> authenticating
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1150] device (p2p-dev-wlp13s0): supplicant management interface state: disconnected -> authenticating
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1151] device (wlp20s0u5): supplicant interface state: authenticating -> associating
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1151] device (p2p-dev-wlp20s0u5): supplicant management interface state: authenticating -> associating
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1194] device (wlp13s0): supplicant interface state: authenticating -> associating
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1194] device (p2p-dev-wlp13s0): supplicant management interface state: authenticating -> associating
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1777] device (wlp20s0u5): supplicant interface state: associating -> associated
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1777] device (p2p-dev-wlp20s0u5): supplicant management interface state: associating -> associated
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1779] device (wlp13s0): supplicant interface state: associating -> associated
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.1779] device (p2p-dev-wlp13s0): supplicant management interface state: associating -> associated
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.4113] device (wlp20s0u5): supplicant interface state: associated -> completed
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.4114] device (wlp20s0u5): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "eduroam"
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.4114] device (p2p-dev-wlp20s0u5): supplicant management interface state: associated -> completed
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.4114] device (wlp20s0u5): state change: config -> ip-config (reason 'none', managed-type: 'full')
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.4117] dhcp4 (wlp20s0u5): activation: beginning transaction (timeout in 45 seconds)
Dec 03 17:48:51 mainstay NetworkManager[633]: <info>  [1764784131.4128] dhcp4 (wlp20s0u5): dhcpcd started with pid 702
Dec 03 17:48:51 mainstay dhcpcd[702]: dhcpcd-10.3.0 starting
Dec 03 17:48:51 mainstay dhcpcd[703]: DUID 00:01:00:01:2e:f2:e4:cb:54:07:7d:7f:3c:a1
Dec 03 17:48:51 mainstay dhcpcd[703]: wlp20s0u5: connected to Access Point: eduroam
Dec 03 17:48:53 mainstay dhcpcd[703]: wlp20s0u5: rebinding lease of 172.24.51.39
Dec 03 17:48:53 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   lease time 3600
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.4481] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39, acd pending
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.5787] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.5802] policy: set 'wlan1-eduroam' (wlp20s0u5) as default for IPv4 routing and DNS
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.5806] device (wlp20s0u5): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.5811] device (wlp20s0u5): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.5811] device (wlp20s0u5): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Dec 03 17:48:53 mainstay NetworkManager[633]: <info>  [1764784133.5814] device (wlp20s0u5): Activation: successful, device activated.
Dec 03 17:48:58 mainstay NetworkManager[633]: <info>  [1764784138.6922] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 03 17:49:15 mainstay NetworkManager[633]: <warn>  [1764784155.4911] device (wlp13s0): Activation: (wifi) association took too long
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4911] device (wlp13s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Dec 03 17:49:15 mainstay NetworkManager[633]: <warn>  [1764784155.4913] device (wlp13s0): Activation: (wifi) asking for new secrets
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4921] device (wlp13s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4922] device (wlp13s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4922] device (wlp13s0): Activation: (wifi) connection 'wlan0-eduroam' has security, and secrets exist.  No new secrets needed.
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'ssid' value 'eduroam'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'scan_ssid' value '1'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'bssid' value 'A4:00:4E:05:06:2D'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'password' value '<hidden>'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'eap' value 'PEAP'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'fragment_size' value '1266'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'phase2' value 'auth=MSCHAPV2'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'identity' value 'u1705507@warwick.ac.uk'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.4923] Config: added 'proactive_key_caching' value '1'
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.5915] device (wlp13s0): supplicant interface state: associated -> disconnected
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.5916] device (p2p-dev-wlp13s0): supplicant management interface state: associated -> disconnected
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.5974] device (wlp13s0): supplicant interface state: disconnected -> scanning
Dec 03 17:49:15 mainstay NetworkManager[633]: <info>  [1764784155.5974] device (p2p-dev-wlp13s0): supplicant management interface state: disconnected -> scanning
Dec 03 17:49:18 mainstay NetworkManager[633]: <info>  [1764784158.2130] device (wlp13s0): supplicant interface state: scanning -> authenticating
Dec 03 17:49:18 mainstay NetworkManager[633]: <info>  [1764784158.2130] device (p2p-dev-wlp13s0): supplicant management interface state: scanning -> authenticating
Dec 03 17:49:18 mainstay NetworkManager[633]: <info>  [1764784158.2170] device (wlp13s0): supplicant interface state: authenticating -> associating
Dec 03 17:49:18 mainstay NetworkManager[633]: <info>  [1764784158.2170] device (p2p-dev-wlp13s0): supplicant management interface state: authenticating -> associating
Dec 03 17:49:18 mainstay NetworkManager[633]: <info>  [1764784158.2749] device (wlp13s0): supplicant interface state: associating -> associated
Dec 03 17:49:18 mainstay NetworkManager[633]: <info>  [1764784158.2749] device (p2p-dev-wlp13s0): supplicant management interface state: associating -> associated
Dec 03 17:49:40 mainstay NetworkManager[633]: <warn>  [1764784180.4927] device (wlp13s0): Activation: (wifi) association took too long
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4928] device (wlp13s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Dec 03 17:49:40 mainstay NetworkManager[633]: <warn>  [1764784180.4930] device (wlp13s0): Activation: (wifi) asking for new secrets
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4934] device (wlp13s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4935] device (wlp13s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] device (wlp13s0): Activation: (wifi) connection 'wlan0-eduroam' has security, and secrets exist.  No new secrets needed.
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'ssid' value 'eduroam'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'scan_ssid' value '1'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'bssid' value 'A4:00:4E:05:06:2D'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'password' value '<hidden>'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'eap' value 'PEAP'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'fragment_size' value '1266'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'phase2' value 'auth=MSCHAPV2'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'identity' value 'u1705507@warwick.ac.uk'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.4936] Config: added 'proactive_key_caching' value '1'
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.5975] device (wlp13s0): supplicant interface state: associated -> disconnected
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.5975] device (p2p-dev-wlp13s0): supplicant management interface state: associated -> disconnected
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.6032] device (wlp13s0): supplicant interface state: disconnected -> scanning
Dec 03 17:49:40 mainstay NetworkManager[633]: <info>  [1764784180.6032] device (p2p-dev-wlp13s0): supplicant management interface state: disconnected -> scanning
Dec 03 17:49:43 mainstay NetworkManager[633]: <info>  [1764784183.2376] device (wlp13s0): supplicant interface state: scanning -> authenticating
Dec 03 17:49:43 mainstay NetworkManager[633]: <info>  [1764784183.2377] device (p2p-dev-wlp13s0): supplicant management interface state: scanning -> authenticating
Dec 03 17:49:43 mainstay NetworkManager[633]: <info>  [1764784183.2419] device (wlp13s0): supplicant interface state: authenticating -> associating
Dec 03 17:49:43 mainstay NetworkManager[633]: <info>  [1764784183.2419] device (p2p-dev-wlp13s0): supplicant management interface state: authenticating -> associating
Dec 03 17:49:43 mainstay NetworkManager[633]: <info>  [1764784183.3019] device (wlp13s0): supplicant interface state: associating -> associated
Dec 03 17:49:43 mainstay NetworkManager[633]: <info>  [1764784183.3019] device (p2p-dev-wlp13s0): supplicant management interface state: associating -> associated
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0459] manager: (tap0): new Tun device (/org/freedesktop/NetworkManager/Devices/7)
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0483] device (tap0): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0485] device (tap0): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0487] device (tap0): Activation: starting connection 'tap0' (c7af25ca-9f9d-4fbe-8f82-79ebc176926f)
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0488] device (tap0): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0488] device (tap0): state change: prepare -> config (reason 'none', managed-type: 'external')
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0488] device (tap0): state change: config -> ip-config (reason 'none', managed-type: 'external')
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0489] device (tap0): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0658] device (tap0): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0658] device (tap0): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Dec 03 17:49:48 mainstay NetworkManager[633]: <info>  [1764784188.0659] device (tap0): Activation: successful, device activated.
Dec 03 17:50:05 mainstay NetworkManager[633]: <warn>  [1764784205.4937] device (wlp13s0): Activation: (wifi) association took too long
Dec 03 17:50:05 mainstay NetworkManager[633]: <info>  [1764784205.4937] device (wlp13s0): state change: config -> failed (reason 'no-secrets', managed-type: 'full')
Dec 03 17:50:05 mainstay NetworkManager[633]: <warn>  [1764784205.4939] device (wlp13s0): Activation: failed for connection 'wlan0-eduroam'
Dec 03 17:50:05 mainstay NetworkManager[633]: <info>  [1764784205.4940] device (wlp13s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Dec 03 17:50:05 mainstay NetworkManager[633]: <info>  [1764784205.5990] device (wlp13s0): supplicant interface state: associated -> disconnected
Dec 03 17:50:05 mainstay NetworkManager[633]: <info>  [1764784205.5990] device (p2p-dev-wlp13s0): supplicant management interface state: associated -> disconnected
Dec 03 17:50:08 mainstay NetworkManager[633]: <info>  [1764784208.2119] manager: startup complete
Dec 03 18:41:23 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 03 18:41:23 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5755] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   lease time 3600
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 03 18:41:23 mainstay NetworkManager[633]: <info>  [1764787283.5756] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 03 19:33:53 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 03 19:33:53 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   lease time 3600
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 03 19:33:53 mainstay NetworkManager[633]: <info>  [1764790433.6998] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 03 20:26:23 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 03 20:26:23 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7619] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7619] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7619] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7619] dhcp4 (wlp20s0u5):   lease time 3600
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7620] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7620] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7620] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7620] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7620] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7620] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 03 20:26:23 mainstay NetworkManager[633]: <info>  [1764793583.7620] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 03 21:18:53 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 03 21:18:53 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8970] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8970] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8970] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8970] dhcp4 (wlp20s0u5):   lease time 3600
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8971] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8971] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8971] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8971] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8971] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8971] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 03 21:18:53 mainstay NetworkManager[633]: <info>  [1764796733.8971] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 03 22:11:23 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 03 22:11:24 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   lease time 3600
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 03 22:11:24 mainstay NetworkManager[633]: <info>  [1764799884.0418] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 03 23:03:54 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 03 23:03:54 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   lease time 3600
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 03 23:03:54 mainstay NetworkManager[633]: <info>  [1764803034.2799] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 03 23:56:24 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 03 23:56:24 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   lease time 3600
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 03 23:56:24 mainstay NetworkManager[633]: <info>  [1764806184.3402] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 00:48:54 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 00:48:54 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4660] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4660] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4660] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4660] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4661] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4661] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4661] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4661] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4661] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4661] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 00:48:54 mainstay NetworkManager[633]: <info>  [1764809334.4661] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 01:41:24 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 01:41:24 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5911] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 01:41:24 mainstay NetworkManager[633]: <info>  [1764812484.5912] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 02:33:54 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 02:33:54 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7227] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 02:33:54 mainstay NetworkManager[633]: <info>  [1764815634.7228] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 03:26:24 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 03:26:24 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7492] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7492] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7492] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7492] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7492] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7492] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7492] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7493] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7493] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7493] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 03:26:24 mainstay NetworkManager[633]: <info>  [1764818784.7493] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 04:18:54 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 04:18:54 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9212] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9212] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9212] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9212] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9212] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9212] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9212] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9212] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9213] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9213] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 04:18:54 mainstay NetworkManager[633]: <info>  [1764821934.9213] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 05:11:24 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 05:11:25 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 05:11:25 mainstay NetworkManager[633]: <info>  [1764825085.0479] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 06:03:55 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 06:03:55 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1846] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1846] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 06:03:55 mainstay NetworkManager[633]: <info>  [1764828235.1847] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 06:56:25 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 06:56:25 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3128] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 06:56:25 mainstay NetworkManager[633]: <info>  [1764831385.3129] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 07:48:55 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 07:48:55 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3463] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 07:48:55 mainstay NetworkManager[633]: <info>  [1764834535.3464] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 08:41:25 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 08:41:25 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4750] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4750] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4750] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4751] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4751] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4751] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4751] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4751] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4751] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4751] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 08:41:25 mainstay NetworkManager[633]: <info>  [1764837685.4751] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 09:33:55 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 09:33:55 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6018] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 09:33:55 mainstay NetworkManager[633]: <info>  [1764840835.6019] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 10:26:25 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 10:26:25 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 10:26:25 mainstay NetworkManager[633]: <info>  [1764843985.7290] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 11:18:55 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 11:18:55 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8561] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 11:18:55 mainstay NetworkManager[633]: <info>  [1764847135.8562] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 12:11:25 mainstay dhcpcd[703]: wlp20s0u5: failed to renew DHCP, rebinding
Dec 04 12:11:26 mainstay dhcpcd[703]: wlp20s0u5: leased 172.24.51.39 for 3600 seconds
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   address 172.24.51.39
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   plen 17 (255.255.128.0)
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   gateway 172.24.0.1
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   lease time 3600
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   hostname 'mainstay'
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   nameserver '137.205.205.129'
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   nameserver '137.205.205.100'
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   domain name 'warwick.ac.uk'
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   domain search 'wpd.warwick.ac.uk'
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5):   domain search 'warwick.ac.uk'
Dec 04 12:11:26 mainstay NetworkManager[633]: <info>  [1764850286.0143] dhcp4 (wlp20s0u5): state changed new lease, address=172.24.51.39
Dec 04 12:20:27 mainstay NetworkManager[633]: <warn>  [1764850827.4932] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:22:28 mainstay NetworkManager[633]: <warn>  [1764850948.4979] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:24:29 mainstay NetworkManager[633]: <warn>  [1764851069.4922] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:26:30 mainstay NetworkManager[633]: <warn>  [1764851190.4971] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:28:31 mainstay NetworkManager[633]: <warn>  [1764851311.4986] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:30:32 mainstay NetworkManager[633]: <warn>  [1764851432.4950] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:32:33 mainstay NetworkManager[633]: <warn>  [1764851553.4951] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:34:34 mainstay NetworkManager[633]: <warn>  [1764851674.4991] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:36:35 mainstay NetworkManager[633]: <warn>  [1764851795.4946] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:38:36 mainstay NetworkManager[633]: <warn>  [1764851916.4920] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:40:37 mainstay NetworkManager[633]: <warn>  [1764852037.4968] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:42:38 mainstay NetworkManager[633]: <warn>  [1764852158.4913] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:44:39 mainstay NetworkManager[633]: <warn>  [1764852279.4968] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:46:40 mainstay NetworkManager[633]: <warn>  [1764852400.4989] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:48:41 mainstay NetworkManager[633]: <warn>  [1764852521.4949] sup-iface[4973115e7dfc6065,0,wlp13s0]: request-scan: could not get scan request result: Timeout was reached
Dec 04 12:49:15 mainstay NetworkManager[633]: <info>  [1764852555.8669] device (wlp20s0u5): ip:dhcp4: restarting
Dec 04 12:49:15 mainstay NetworkManager[633]: <info>  [1764852555.8669] dhcp4 (wlp20s0u5): canceled DHCP transaction, DHCP client pid 702
Dec 04 12:49:15 mainstay dhcpcd[703]: received SIGTERM, stopping
Dec 04 12:49:15 mainstay NetworkManager[633]: <info>  [1764852555.8669] dhcp4 (wlp20s0u5): activation: beginning transaction (timeout in 45 seconds)
Dec 04 12:49:15 mainstay dhcpcd[703]: wlp20s0u5: removing interface
Dec 04 12:49:15 mainstay NetworkManager[633]: <info>  [1764852555.8669] dhcp4 (wlp20s0u5): state changed no lease
Dec 04 12:49:15 mainstay NetworkManager[633]: <info>  [1764852555.8670] dhcp4 (wlp20s0u5): activation: beginning transaction (timeout in 45 seconds)
Dec 04 12:49:15 mainstay NetworkManager[633]: <info>  [1764852555.8677] dhcp4 (wlp20s0u5): dhcpcd started with pid 5416
Dec 04 12:49:15 mainstay NetworkManager[633]: <warn>  [1764852555.8686] dhcp-listener: dhcp-event: (pid 702) unhandled DHCP event for interface wlp20s0u5
Dec 04 12:49:15 mainstay NetworkManager[633]: <info>  [1764852555.8689] dhcp4 (wlp20s0u5): client pid 5416 exited with status 0
Dec 04 12:49:15 mainstay NetworkManager[633]: <info>  [1764852555.8689] dhcp4 (wlp20s0u5): state changed no lease
Dec 04 12:49:16 mainstay NetworkManager[633]: <warn>  [1764852556.0890] dhcp-listener: dhcp-event: (pid 702) unhandled DHCP event for interface wlp20s0u5
Dec 04 12:49:16 mainstay dhcpcd[703]: dhcpcd exited

Any clues as to what is going on?

Last edited by HenryJia (2025-12-05 18:20:52)

seth · 2025-12-05 20:44:26

This is the journalctl output from boot to when NetworkManager stops working

This only shows NM and dhcpcd, not even wpa_supplicant. Don't grep unless you know what you're specifically grepping for.
The unfiltered journal around the critical time will provide more information than this.

Big red flag:

openvpn-client@central-iceland.service | multi-user.target.wants

Do you get this w/o the VPN?

HenryJia · 2025-12-10 01:47:56

So I had a play around, this is the full journalctl around the time it fails

Dec 09 15:18:03 mainstay dhcpcd[701]: wlan1: leased 172.24.22.113 for 3600 seconds
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8257] dhcp4 (wlan1):   address 172.24.22.113
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8257] dhcp4 (wlan1):   plen 17 (255.255.128.0)
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8257] dhcp4 (wlan1):   gateway 172.24.0.1
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8258] dhcp4 (wlan1):   lease time 3600
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8258] dhcp4 (wlan1):   hostname 'mainstay'
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8258] dhcp4 (wlan1):   nameserver '137.205.205.129'
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8258] dhcp4 (wlan1):   nameserver '137.205.205.100'
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8258] dhcp4 (wlan1):   domain name 'warwick.ac.uk'
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8258] dhcp4 (wlan1):   domain search 'wpd.warwick.ac.uk'
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8258] dhcp4 (wlan1):   domain search 'warwick.ac.uk'
Dec 09 15:18:03 mainstay NetworkManager[629]: <info>  [1765293483.8258] dhcp4 (wlan1): state changed new lease, address=172.24.22.113
Dec 09 15:18:03 mainstay systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 09 15:18:03 mainstay systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 09 15:18:13 mainstay systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 09 15:34:48 mainstay wpa_supplicant[675]: wlan1: RSN: Group rekeying completed with a4:00:4e:05:06:23 [GTK=CCMP]
Dec 09 16:10:33 mainstay dhcpcd[701]: wlan1: failed to renew DHCP, rebinding
Dec 09 16:10:33 mainstay dhcpcd[701]: wlan1: leased 172.24.22.113 for 3600 seconds
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9784] dhcp4 (wlan1):   address 172.24.22.113
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9784] dhcp4 (wlan1):   plen 17 (255.255.128.0)
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9784] dhcp4 (wlan1):   gateway 172.24.0.1
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9784] dhcp4 (wlan1):   lease time 3600
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9784] dhcp4 (wlan1):   hostname 'mainstay'
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9784] dhcp4 (wlan1):   nameserver '137.205.205.129'
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9785] dhcp4 (wlan1):   nameserver '137.205.205.100'
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9785] dhcp4 (wlan1):   domain name 'warwick.ac.uk'
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9785] dhcp4 (wlan1):   domain search 'wpd.warwick.ac.uk'
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9785] dhcp4 (wlan1):   domain search 'warwick.ac.uk'
Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9785] dhcp4 (wlan1): state changed new lease, address=172.24.22.113
Dec 09 16:10:33 mainstay systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 09 16:10:33 mainstay systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 09 16:10:44 mainstay systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 09 16:12:21 mainstay openvpn[753]: VERIFY OK: depth=1, CN=Easy-RSA CA
Dec 09 16:12:21 mainstay openvpn[753]: VERIFY KU OK
Dec 09 16:12:21 mainstay openvpn[753]: Validating certificate extended key usage
Dec 09 16:12:21 mainstay openvpn[753]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Dec 09 16:12:21 mainstay openvpn[753]: VERIFY EKU OK
Dec 09 16:12:21 mainstay openvpn[753]: VERIFY OK: depth=0, CN=server
Dec 09 16:12:21 mainstay openvpn[753]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 384 bits ECsecp384r1, signature: ecdsa-with-SHA512, peer temporary key: 253 bits X25519
Dec 09 16:20:32 mainstay NetworkManager[629]: <warn>  [1765297232.8245] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:22:33 mainstay NetworkManager[629]: <warn>  [1765297353.8267] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:24:34 mainstay NetworkManager[629]: <warn>  [1765297474.8271] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:26:35 mainstay NetworkManager[629]: <warn>  [1765297595.8247] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:28:36 mainstay NetworkManager[629]: <warn>  [1765297716.8264] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:30:37 mainstay NetworkManager[629]: <warn>  [1765297837.8255] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:32:38 mainstay NetworkManager[629]: <warn>  [1765297958.8230] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:34:39 mainstay NetworkManager[629]: <warn>  [1765298079.8270] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:34:50 mainstay NetworkManager[629]: <info>  [1765298090.9821] device (wlan1): ip:dhcp4: restarting
Dec 09 16:34:50 mainstay NetworkManager[629]: <info>  [1765298090.9821] dhcp4 (wlan1): canceled DHCP transaction, DHCP client pid 700
Dec 09 16:34:50 mainstay kernel: wlan1: deauthenticated from a4:00:4e:05:06:23 (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
Dec 09 16:34:50 mainstay dhcpcd[701]: received SIGTERM, stopping
Dec 09 16:34:50 mainstay NetworkManager[629]: <info>  [1765298090.9821] dhcp4 (wlan1): activation: beginning transaction (timeout in 45 seconds)
Dec 09 16:34:50 mainstay dhcpcd[701]: wlan1: removing interface
Dec 09 16:34:50 mainstay NetworkManager[629]: <info>  [1765298090.9821] dhcp4 (wlan1): state changed no lease
Dec 09 16:34:50 mainstay NetworkManager[629]: <info>  [1765298090.9822] dhcp4 (wlan1): activation: beginning transaction (timeout in 45 seconds)
Dec 09 16:34:50 mainstay NetworkManager[629]: <info>  [1765298090.9830] dhcp4 (wlan1): dhcpcd started with pid 5555
Dec 09 16:34:50 mainstay NetworkManager[629]: <warn>  [1765298090.9839] dhcp-listener: dhcp-event: (pid 700) unhandled DHCP event for interface wlan1
Dec 09 16:34:50 mainstay NetworkManager[629]: <info>  [1765298090.9842] dhcp4 (wlan1): client pid 5555 exited with status 0
Dec 09 16:34:50 mainstay NetworkManager[629]: <info>  [1765298090.9842] dhcp4 (wlan1): state changed no lease
Dec 09 16:34:51 mainstay NetworkManager[629]: <warn>  [1765298091.0617] dhcp-listener: dhcp-event: (pid 700) unhandled DHCP event for interface wlan1
Dec 09 16:34:51 mainstay dhcpcd[701]: dhcpcd exited
Dec 09 16:34:55 mainstay openvpn[753]: [server] Inactivity timeout (--ping-restart), restarting
Dec 09 16:34:55 mainstay openvpn[753]: net_route_v4_del: 89.147.108.154/32 via 172.24.0.1 dev [NULL] table 0 metric -1
Dec 09 16:34:55 mainstay openvpn[753]: sitnl_send: rtnl: generic error (-3): No such process
Dec 09 16:34:55 mainstay openvpn[753]: ERROR: Linux route delete command failed
Dec 09 16:34:55 mainstay openvpn[753]: net_route_v4_del: 0.0.0.0/1 via 10.8.0.1 dev [NULL] table 0 metric -1
Dec 09 16:34:55 mainstay openvpn[753]: net_route_v4_del: 128.0.0.0/1 via 10.8.0.1 dev [NULL] table 0 metric -1
Dec 09 16:34:55 mainstay openvpn[753]: Closing TUN/TAP interface
Dec 09 16:34:55 mainstay openvpn[753]: net_addr_v4_del: 10.8.0.3 dev tap0
Dec 09 16:34:55 mainstay NetworkManager[629]: <info>  [1765298095.1011] device (tap0): state change: activated -> unmanaged (reason 'unmanaged', managed-type: 'removed')
Dec 09 16:34:55 mainstay systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 09 16:34:55 mainstay openvpn[753]: SIGUSR1[soft,ping-restart] received, process restarting
Dec 09 16:34:55 mainstay openvpn[753]: Restart pause, 1 second(s)
Dec 09 16:34:55 mainstay systemd[1]: Started Network Manager Script Dispatcher Service.

I've not tried without OpenVPN. I'm pretty certain the VPN isn't the thing interfering here because I wrote the VPN configuration, and it's never interfered with NetworkManager to my experience. It's also what makes it accessible to me remotely anyway so I can't really turn it off. We can also see that the VPN just encounters a connection error after NetworkManager cuts out because wpa_supplicant keeps timing out

seth · 2025-12-10 08:23:28

Last wpa_Supplicant message:

Dec 09 15:34:48 mainstay wpa_supplicant[675]: wlan1: RSN: Group rekeying completed with a4:00:4e:05:06:23 [GTK=CCMP]

35 minutes later dhcpcd renews the lease

Dec 09 16:10:33 mainstay NetworkManager[629]: <info>  [1765296633.9785] dhcp4 (wlan1): state changed new lease, address=172.24.22.113

2 minutes later openvpn updates

Dec 09 16:12:21 mainstay openvpn[753]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 384 bits ECsecp384r1, signature: ecdsa-with-SHA512, peer temporary key: 253 bits X25519

8 minutes later NM fails

Dec 09 16:20:32 mainstay NetworkManager[629]: <warn>  [1765297232.8245] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:22:33 mainstay NetworkManager[629]: <warn>  [1765297353.8267] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:24:34 mainstay NetworkManager[629]: <warn>  [1765297474.8271] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:26:35 mainstay NetworkManager[629]: <warn>  [1765297595.8247] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:28:36 mainstay NetworkManager[629]: <warn>  [1765297716.8264] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:30:37 mainstay NetworkManager[629]: <warn>  [1765297837.8255] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:32:38 mainstay NetworkManager[629]: <warn>  [1765297958.8230] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached
Dec 09 16:34:39 mainstay NetworkManager[629]: <warn>  [1765298079.8270] sup-iface[f15ead0073cddd5a,0,wlan0]: request-scan: could not get scan request result: Timeout was reached

what scan requests?
Since this is on a 2 minute frequency, wpa_supplicant probably stopped responding 16:18

I'm pretty certain the VPN isn't the thing interfering here

Ultimately, get "very certain" and run w/o

Before that,

Dec 09 16:10:33 mainstay dhcpcd[701]: wlan1: failed to renew DHCP, rebinding
Dec 09 16:10:33 mainstay dhcpcd[701]: wlan1: leased 172.24.22.113 for 3600 seconds

is fishy - dhcpcd asks in time (does this pattern show up frequently?)

There might be something off w/ the latest dhcpcd release, https://github.com/NetworkConfiguration … issues/560
Try to use the internal dhcp client or dhclient and see whether the issue remains.

-thc · 2025-12-10 08:23:30

HenryJia wrote:

I've not tried without OpenVPN. I'm pretty certain the VPN isn't the thing interfering here because I wrote the VPN configuration, and it's never interfered with NetworkManager to my experience.

That's an unfounded assumption. OpenVPN will alter the routing table and (in client mode) the DNS resolving and thus collide with NetworkManager.
I strongly recommend to add the OpenVPN client connection to NetworkManager.

There is a glitch in your OpenVPN configuration. The IP addresses 10.8.0.x are used by OpenVPN in "tunnel" mode - with a "tun" device. A "tap" device is used in "bridge" mode.

To sum it up: You have a PC running 24/7 somewhere in the vicinity of the university of Warwick connected to eduroam via WiFi that maintains an OpenVPN client connection in tunnel mode (the endpoint's IP is in Iceland) to enable remote access to this PC? Are you absolutely sure that the terms & conditions for eduroam at Warwick allow this setup? Because the errors/timeouts beginning at 16:20 look to me as if the WiFi Access point simply refuses to talk to your PC any longer.

HenryJia · 2025-12-10 15:59:40

-thc wrote:

To sum it up: You have a PC running 24/7 somewhere in the vicinity of the university of Warwick connected to eduroam via WiFi that maintains an OpenVPN client connection in tunnel mode (the endpoint's IP is in Iceland) to enable remote access to this PC? Are you absolutely sure that the terms & conditions for eduroam at Warwick allow this setup? Because the errors/timeouts beginning at 16:20 look to me as if the WiFi Access point simply refuses to talk to your PC any longer.

Yes, this is allowed by the acceptable use policy of the university. The university's Acceptable Use Policy doesn't list anything regarding VPNs. This machine is a workstation of mine used to support my work in computational chemistry and machine learning, so it certainly doesn't contravene any of the terms and conditions.

In addition, I'm pretty certain it's wpa_supplicant that ceases to respond. I tested this by bringing up a hotspot on my phone and ordering wpa_supplicant to do a scan via Network Manager. This yields no response at all. nmcli is just showing the last scan results from the last time wpa_supplicant was responsive.

seth wrote:

Before that,
Dec 09 16:10:33 mainstay dhcpcd[701]: wlan1: failed to renew DHCP, rebinding
Dec 09 16:10:33 mainstay dhcpcd[701]: wlan1: leased 172.24.22.113 for 3600 seconds
is fishy - dhcpcd asks in time (does this pattern show up frequently?)

Yes, that does show up regularly in the journalctl when NetworkManager is connected. I presume that is normal.

seth wrote:

Try to use the internal dhcp client or dhclient and see whether the issue remains.

That was what I used initially, which had the same issue, which is why I tried switching to dhcpcd to see if it would go away.

I'll give running without OpenVPN a go, but that does kind of defeat the point of this. I want to be able to work remotely to this headless workstation.

My current "temporary solution that will probably become permanent" is to just add a RuntimeMaxSec=8h to the wpa_supplicant service to force NetworkManager to restart it every 8 hours or so to deal with this.

seth · 2025-12-10 16:48:54

I'll give running without OpenVPN a go, but that does kind of defeat the point of this.

The immediate objective is just to figure whether it's coming from there at all.
If so, we at least know where to look at and if not we'll have to shop around for other causes.

Arch Linux

#1 2025-12-03 17:13:28

wpa_supplicant seems to require regular restarts with network manager

#2 2025-12-03 18:29:00

Re: wpa_supplicant seems to require regular restarts with network manager

#3 2025-12-03 19:23:43

Re: wpa_supplicant seems to require regular restarts with network manager

#4 2025-12-05 18:17:47

Re: wpa_supplicant seems to require regular restarts with network manager

#5 2025-12-05 20:44:26

Re: wpa_supplicant seems to require regular restarts with network manager

#6 2025-12-10 01:47:56

Re: wpa_supplicant seems to require regular restarts with network manager

#7 2025-12-10 08:23:28

Re: wpa_supplicant seems to require regular restarts with network manager

#8 2025-12-10 08:23:30

Re: wpa_supplicant seems to require regular restarts with network manager

#9 2025-12-10 15:59:40

Re: wpa_supplicant seems to require regular restarts with network manager

#10 2025-12-10 16:48:54

Re: wpa_supplicant seems to require regular restarts with network manager

Board footer