Linux Crashes my Router

ohgodmanyo · 2025-06-11 03:05:14

I’m using arch linux with networkmanager. Swapping backend to iwd didn’t help the issue. I also tried disabling 11ax in iwlwifi. My issue is that any time I do any type of web browsing where i’m loading multiple websites my entire network crashes and reboots. I used tcp dump to see if the issue was dns spam and it sends like 2-3 requests per website so it doesn’t send that many. Hardly ever have issues when gaming or downloading things. Crashes all the time using librewolf and also when i was using a music rip tool when it was making lots of http requests. My router is a rogers xfinity and it flashes orange for 1-2 minutes on every crash. This only happens on linux all my others devices don’t do this. I should note that this never happens on chromium but happens on (but not limited to) librewolf which is a major pain.

output of journalctl -u NetworkManager -f and journalctl -u iwd -f

removed some mac addresses but heres what both of those outputs show right before during and after crash

NetworkManager:

Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3488] device (wlan0): new IWD device state is disconnected 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3490] device (wlan0): state change: activated -> failed (reason 'supplicant-disconnect', managed-type: 'full') 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3492] manager: NetworkManager state is now DISCONNECTED 
Jun 10 22:25:56 vonpc NetworkManager[566]: <warn> [1749608756.3493] device (wlan0): Activation: failed for connection 'homerouter2' 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3498] device (wlan0): state change: failed -> disconnected (reason 'none', managed-type: 'full') 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3500] dhcp4 (wlan0): canceled DHCP transaction 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3500] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds) 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3501] dhcp4 (wlan0): state changed no lease 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3501] dhcp6 (wlan0): canceled DHCP transaction 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3501] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds) 
Jun 10 22:25:56 vonpc NetworkManager[566]: <info> [1749608756.3502] dhcp6 (wlan0): state changed no lease

iwd: 
Jun 10 22:25:56 vonpc iwd[637]: Received Deauthentication event, reason: 4, from_ap: false 
Jun 10 22:25:56 vonpc iwd[637]: event: disconnect-info, reason: 4 
Jun 10 22:25:56 vonpc iwd[637]: event: state, old: connected, new: disconnected 
Jun 10 22:25:56 vonpc iwd[637]: event: state, old: disconnected, new: autoconnect_quick 
Jun 10 22:25:56 vonpc iwd[637]: event: state, old: autoconnect_quick, new: autoconnect_full 
Jun 10 22:26:00 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:00 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:00 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:00 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:00 vonpc iwd[637]: wiphy_estimate_data_rate() failed 
Jun 10 22:26:13 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:13 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:13 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:13 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:13 vonpc iwd[637]: wiphy_estimate_data_rate() failed 
Jun 10 22:26:37 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:37 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:37 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:37 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:26:37 vonpc iwd[637]: wiphy_estimate_data_rate() failed 
Jun 10 22:27:21 vonpc iwd[637]: wiphy_estimate_data_rate() failed 
Jun 10 22:28:44 vonpc iwd[637]: wiphy_estimate_data_rate() failed 
Jun 10 22:28:44 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:28:44 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:28:44 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:28:44 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:28:44 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:28:44 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:28:44 vonpc iwd[637]: invalid HE capabilities for 
Jun 10 22:28:44 vonpc iwd[637]: event: connect-info, ssid: homerouter2, bss:, signal: -64, load: 0/255 
Jun 10 22:28:44 vonpc iwd[637]: event: state, old: autoconnect_full, new: connecting (auto) 
Jun 10 22:28:44 vonpc iwd[637]: event: state, old: connecting (auto), new: connected

I will also show the output of journalctl -u systemd-resolved -f:

Jun 10 23:00:13 vonpc systemd-resolved[359]: wlan0: Bus client reset search domain list.
Jun 10 23:00:13 vonpc systemd-resolved[359]: wlan0: Bus client set default route setting: no
Jun 10 23:00:13 vonpc systemd-resolved[359]: wlan0: Bus client reset DNS server list.
Jun 10 23:00:13 vonpc systemd-resolved[359]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.
Jun 10 23:03:04 vonpc systemd-resolved[359]: wlan0: Bus client set default route setting: yes
Jun 10 23:03:04 vonpc systemd-resolved[359]: wlan0: Bus client set DNS server list to: 192.168.1.1
Jun 10 23:03:20 vonpc systemd-resolved[359]: wlan0: Bus client set default route setting: no
Jun 10 23:03:20 vonpc systemd-resolved[359]: wlan0: Bus client reset DNS server list.
Jun 10 23:03:22 vonpc systemd-resolved[359]: Switching to fallback DNS server 1.1.1.1#cloudflare-dns.com.
Jun 10 23:03:22 vonpc systemd-resolved[359]: wlan0: Bus client set search domain list to: phub.net.cable.rogers.com
Jun 10 23:03:22 vonpc systemd-resolved[359]: wlan0: Bus client set default route setting: yes
Jun 10 23:03:22 vonpc systemd-resolved[359]: wlan0: Bus client set DNS server list to: lalalala redacted bc its some ip addresses

as you can see at 23:00 it crashes and it comes back at 23:03. any potential solutions?

Last edited by ohgodmanyo (2025-06-11 13:06:14)

seth · 2025-06-11 06:28:04

Please use [code][/code] tags. Edit your post in this regard.
You local system is probably of mild relevance only if the router crashes (that's a router bug) but for a general overview please post the output of

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

and your complete system journal for the boot (after crashing the router):

sudo journalctl -b | curl -F 'file=@-' 0x0.st

because isolated messages out of context on a non-affected system won't explain much here.

Some APs seriously don't like https://wiki.archlinux.org/title/Networ … domization so disable that and also NM defaults to wpa_supplicant, if you've not followed https://wiki.archlinux.org/title/Networ … Fi_backend you might confuse the router w/ frequent re-associations from both carrier suppliers.

lalalala redacted bc its some ip addresses

which is either gonna be some LAN IP or ISPs DNS, not your WAN IP

If your're trying to conceal anything because you don't understand it, please use syntactically correct pseudonyms, ie. 123.45.67.89 => 111.11.11.11, 98.76.54.32 => 22.22.22.22, do not anonymize tokens by using "xxx" everywhere and also don#t inject silly tokens.

Arch Linux

#1 2025-06-11 03:05:14

Linux Crashes my Router

#2 2025-06-11 06:28:04

Re: Linux Crashes my Router

Board footer