GL-AX1800 Flint on Linux: WAN disconnects randomly

Routers
1

Hello! Im having a strange issue with my new Flint. First of all, i love the router, it actually works great and im still learning how to use it.

My network setup
ISP Router ------- FLINT ------ Devices (WAN/LAN)

Issue: Random disconnects on WAN or LAN. No matter the router mode

On my current archlinux box (and another fresh install in a new ssd both with NetworkManager and KDE 6 desktop), is that i keep getting disconnected when i increase the download traffic.
In idle it stays stable, but as soon as i start reproducing an hd video, or a speedtest for example, the connection starts to disconnect and reconnect. I changed cables, tried the router in all modes (repeater, tether, ethernet) and the issue persists, via LAN or WAN. But particularly ONLY on Archlinux... I tried the same connections with Win 10, Win 11 and Ubuntu (also devices: android, TVs, etc), all stable.

Router Firmware Version
4.5.16

Any ideas on how to troubleshoot this in Archlinux? I think the issue may be in NetworkManager, but im using the exact same drivers and config on my Ubuntu box, and this does not happen there... Win 10 mentioned is in the exact same box as my Archlinux install (dual boot) hence, using same network card.

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

2

Dumb questions, is there any update for the Archlinux version?

3

hey thanks for your reply. Not sure if i understood but yes, i keep my system up to date

4

First of all Google it as there are many similar posts for the exact issue! It seems to be related to KDE and network manager. So it is not related to the Flint!

Here is a post that may help you get started:
https://bbs.archlinux.org/viewtopic.php?id=151985
https://bbs.archlinux.org/viewtopic.php?id=291874

If you however prefer to troubleshoot it by yourself you can :

  • Make sure to use an exact network driver version of Ubuntu in Arch.

  • inspect the syslog right after fails.

  • Disable all firewall and security functions on Arch, and test again. You may need also to try wireshark to have deeper insight into the packets prior to failing.

  • try to connect to the network while network manager is disabled.

1 Like
5

Hey @SpitzAX3000 thanks for your reply!
Unfortunately every search (google,, duck, archwiki, ubuntu docs, etc) lead me to nowhere. That's why i came here! Given i'm not that savvy in Networking maybe here i could find someone who already bumped into this issue.

I will try your advices that i have not already tried and will keep you posted.
I know it is not related to Flint or at least i had the same idea that KDE and NetworkManager may be causing this issue.

For this:

I only need to try last 2:
-wireshark (i do not have firewall active and need to review the other possible "security functions")
-connecting with NetworkManager disabled
But im not sure if i will get relevant information or a solution here.

Anyways, thanks again for your reply and your tips.

6

Updates on some more tests:

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 Here i used latest generic kernel, same as Ubuntu Laptop below.
Through Flint, unstable (WAN/LAN).
Through CGN3U Stable (WAN/LAN).

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

Android
Several devices - NO ISSUES

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

journalctl -u NetworkManager | curl -F 'file=@-' 0x0.st[
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

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.

7

Hi,

Thanks for your syslog shared.
I would like to confirm if the devices (Arch & Ubuntu of the PC Nvme/SSD/HDD) can get the IP from Flint (always LAN of router <---> Intel I211 port of PC), or let's say the of attached log is right?

and, you mentioned 'link down' also means that the PC cannot ping the Flint when they running large flow?

8

Hey Bruce! Thanks for your reply. I'm so sorry i did not came here earlier, i completely forgot about this post. Actually i bought Cat6a Certified cables and now it works like a charm. My old Cat5e cables seemed to be the issue.
Thank you very much again for your replies!