[SOLVED] GL-AX1800 Flint on Linux: WAN disconnects constantly

kawaK · 2024-05-28 19:35:46

Hello there, i need some help! Im having a strange issue with my Flint router. I have tried a lot of things already, and done a lot of research but i was not able to find something similar online...
At first i thought it was only an issue on my arch install, but then i set up 2 new installs to test, arch and ubuntu (in extra drives inside my PC), long story short:

My network setup
Then
ISP Router (CGN3U Hitron) ------ Devices (WAN/LAN)

Now
ISP Router (CGN3U Hitron) ------- New Router (GL-AX1800 Flint) ------ Devices (WAN/LAN)
Tested in several different modes: Ethernet, Repeater, Tether. Will use in all modes, most frequent will be Ethernet.

Issue: Random disconnects on WAN or LAN. No matter the ISP's or New Router's mode. Tried setting CGN3U Hitron on bridge mode. Port forwarding to and setting GL-AX1800 Flint as Repeater, and alll of the modes it has.
For GL-AX1800 Flint i have the firmware up to date. Also in all my devices. Kernels up to date (used LTS, zen, generic, a lot of different versions in my different devices).
I have AdGuard and Wireguard enabled on GL-AX1800 Flint Router and works perfect in all devices.
My cables are OK
All Systems ALWAYS up to date (exept for win10)

PC:
NVME with WIN 10 - NO ISSUES
NVME Arch KDE6 - Through Flint, unstable (WAN/LAN). Through CGN3U Stable (WAN/LAN). Latest zen kernel (6.9.2-zen1-1-zen)
SSD Arch GNOME - Through Flint, unstable (WAN/LAN). Through CGN3U Stable (WAN/LAN). Here i also tested latest zen and lts kernels...
HDD Ubuntu KDE6 - Through Flint, unstable (WAN/LAN). Through CGN3U Stable (WAN/LAN). Here i used latest generic kernel, same as Ubuntu Laptop below.

Laptops
Ubuntu GNOME - NO ISSUES (Kernel 5.15.0-107-generic)
Win 11 - NO ISSUES

Android
Several devices - NO ISSUES

Flint Router Firmware Version (OpenWRT)
4.5.16

Controller

lspci | grep Ethernet
05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

Sample Journalctl monitoring when it disconnects:
I can reproduce this for example performing a speed test. As soon as my download bandwidth goes up, it disconnects

journalctl -u NetworkManager -f

may 25 01:18:52 arch NetworkManager[646]: <info>  [1716610732.7481] manager: NetworkManager state is now CONNECTED_GLOBAL
may 25 01:19:05 arch NetworkManager[646]: <info>  [1716610745.9438] device (enp5s0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
may 25 01:19:05 arch NetworkManager[646]: <info>  [1716610745.9438] dhcp4 (enp5s0): canceled DHCP transaction
may 25 01:19:05 arch NetworkManager[646]: <info>  [1716610745.9438] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
may 25 01:19:05 arch NetworkManager[646]: <info>  [1716610745.9438] dhcp4 (enp5s0): state changed no lease
may 25 01:19:05 arch NetworkManager[646]: <info>  [1716610745.9869] manager: NetworkManager state is now DISCONNECTED
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4682] device (enp5s0): carrier: link connected
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4683] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4706] policy: auto-activating connection 'hunabku' (ID)
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4709] device (enp5s0): Activation: starting connection 'hunabku' (ID)
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4710] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4711] manager: NetworkManager state is now CONNECTING
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4712] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4722] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
may 25 01:19:20 arch NetworkManager[646]: <info>  [1716610760.4742] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
may 25 01:19:22 arch NetworkManager[646]: <info>  [1716610762.4766] dhcp4 (enp5s0): state changed new lease, address=<MY IP>, acd pending
may 25 01:19:22 arch NetworkManager[646]: <info>  [1716610762.6365] dhcp4 (enp5s0): state changed new lease, address=<MY IP>
may 25 01:19:22 arch NetworkManager[646]: <info>  [1716610762.6369] policy: set 'hunabku' (enp5s0) as default for IPv4 routing and DNS
may 25 01:19:22 arch NetworkManager[646]: <info>  [1716610762.6410] device (enp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
may 25 01:19:22 arch NetworkManager[646]: <info>  [1716610762.6423] device (enp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
may 25 01:19:22 arch NetworkManager[646]: <info>  [1716610762.6425] device (enp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
may 25 01:19:22 arch NetworkManager[646]: <info>  [1716610762.6428] manager: NetworkManager state is now CONNECTED_SITE
may 25 01:19:22 arch NetworkManager[646]: <info>  [1716610762.6430] device (enp5s0): Activation: successful, device activated.
may 25 01:19:23 arch NetworkManager[646]: <info>  [1716610763.2015] manager: NetworkManager state is now CONNECTED_GLOBAL

$ journalctl -u NetworkManager | curl -F 'file=@-' 0x0.st[
> https://0x0.st/XNTm.txt

$ sudo journalctl -b | curl -F 'file=@-' 0x0.st
> http://0x0.st/XNTb.txt

Any ideas on how to troubleshoot this weird situation? I have tried a lot more things that i may be leaving out just because im kinda lost after all.

Please let me know if and what further information you need in order to get more specific context. Any ideas will be much appreciated!

Thanks in advance!
kawaK

Last edited by kawaK (2024-06-04 13:11:17)

seth · 2024-05-28 22:00:35

Disable the docker/containerd device/vbridge - still an issue?

kawaK · 2024-05-28 22:25:24

Hey seth, thanks for answering! Nope, unfortunately no changes... i removed docker and k8s entirely, rebooted and still same issue.

kawaK · 2024-05-29 03:53:34

^[[Amay 29 00:51:25 arch kernel: igb 0000:05:00.0 enp5s0: igb: enp5s0 NIC Link is Down
may 29 00:51:31 arch NetworkManager[4596]: <info>  [1716954691.9288] device (enp5s0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
may 29 00:51:31 arch NetworkManager[4596]: <info>  [1716954691.9288] dhcp4 (enp5s0): canceled DHCP transaction
may 29 00:51:31 arch NetworkManager[4596]: <info>  [1716954691.9288] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
may 29 00:51:31 arch NetworkManager[4596]: <info>  [1716954691.9288] dhcp4 (enp5s0): state changed no lease
may 29 00:51:31 arch NetworkManager[4596]: <info>  [1716954691.9535] manager: NetworkManager state is now DISCONNECTED
may 29 00:51:31 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
may 29 00:51:31 arch systemd[1]: Started Network Manager Script Dispatcher Service.
may 29 00:51:41 arch systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
may 29 00:51:46 arch kernel: igb 0000:05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1712] device (enp5s0): carrier: link connected
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1714] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1728] policy: auto-activating connection 'hunabku' (ID)
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1731] device (enp5s0): Activation: starting connection 'hunabku' (ID)
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1731] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1734] manager: NetworkManager state is now CONNECTING
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1736] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1746] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
may 29 00:51:46 arch NetworkManager[4596]: <info>  [1716954706.1747] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
may 29 00:51:47 arch plasmashell[4923]: Fontconfig error: Cannot load default config file: No such file: (null)
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.1780] dhcp4 (enp5s0): state changed new lease, address=IP
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.1783] policy: set 'hunabku' (enp5s0) as default for IPv4 routing and DNS
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.1831] device (enp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
may 29 00:51:48 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
may 29 00:51:48 arch systemd[1]: Started Network Manager Script Dispatcher Service.
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.2040] device (enp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.2042] device (enp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.2047] manager: NetworkManager state is now CONNECTED_SITE
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.2049] device (enp5s0): Activation: successful, device activated.
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.2147] audit: op="statistics" interface="enp5s0" ifindex=2 args="2000" pid=1151 uid=1000 result="success"
may 29 00:51:48 arch NetworkManager[4596]: <info>  [1716954708.7530] manager: NetworkManager state is now CONNECTED_GLOBAL

Last edited by kawaK (2024-05-29 03:54:35)

-thc · 2024-05-29 07:15:19

Your GL-AX1800 has 1GBps LAN ports. It's highly suspicious that your box only connects at 100 MBps and loses the connection.

Check you cables, try another router LAN port or insert a small 1GBps router between your box an the router.

kawaK · 2024-06-04 13:12:05

Changed my Cat5e cables to Cat6a Certified and now it works like a charm.
Thanks for all of your replies!

Arch Linux

#1 2024-05-28 19:35:46

[SOLVED] GL-AX1800 Flint on Linux: WAN disconnects constantly

#2 2024-05-28 22:00:35

Re: [SOLVED] GL-AX1800 Flint on Linux: WAN disconnects constantly

#3 2024-05-28 22:25:24

Re: [SOLVED] GL-AX1800 Flint on Linux: WAN disconnects constantly

#4 2024-05-29 03:53:34

Re: [SOLVED] GL-AX1800 Flint on Linux: WAN disconnects constantly

#5 2024-05-29 07:15:19

Re: [SOLVED] GL-AX1800 Flint on Linux: WAN disconnects constantly

#6 2024-06-04 13:12:05

Re: [SOLVED] GL-AX1800 Flint on Linux: WAN disconnects constantly

Board footer