GL-AX1800 Flint often drop WAN connection

Hello,
I just switched my Netgear R7000 (Merlin WRT) for Flint. (WAN mac is made the same).
but I have an issue when ISP cable is plugged directly into Flint - connection drop often.
Configuration:

  • ISP 100Mb RJ45 DHCP
  • No connection issue if R7000 is plugged to ISP’s cable and other devices are connected to R7000
  • No connection issue if R7000 is plugged to ISP’s cable, Flint plugged to LAN port of R7000 and all other devices are connected to Flint
  • Connection drop if ISP’ s cable plugged into Flint (log):
Log

Sat Dec 30 20:31:06 2023 daemon.notice netifd: Network device ‘eth0’ link is down
Sat Dec 30 20:31:06 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity loss
Sat Dec 30 20:31:06 2023 kern.info kernel: [31610.264260] nss-dp 3a001000.dp1 eth0: PHY Link is down
Sat Dec 30 20:31:06 2023 daemon.notice netifd: wan (11661): udhcpc: received SIGTERM
Sat Dec 30 20:31:06 2023 daemon.notice netifd: wan (11661): udhcpc: unicasting a release of to 10.37.126.58
Sat Dec 30 20:31:06 2023 daemon.notice netifd: wan (11661): udhcpc: sending release
Sat Dec 30 20:31:06 2023 daemon.notice netifd: wan (11661): udhcpc: entering released state
Sat Dec 30 20:31:06 2023 daemon.notice netifd: wan (11661): Command failed: Permission denied
Sat Dec 30 20:31:06 2023 daemon.notice netifd: Interface ‘wan’ is now down
Sat Dec 30 20:31:06 2023 daemon.info avahi-daemon[4233]: Withdrawing address record for on eth0.
Sat Dec 30 20:31:06 2023 daemon.info avahi-daemon[4233]: Leaving mDNS multicast group on interface eth0.IPv4 with address .
Sat Dec 30 20:31:06 2023 daemon.notice netifd: Interface ‘wan’ is disabled
Sat Dec 30 20:31:06 2023 daemon.info avahi-daemon[4233]: Interface eth0.IPv4 no longer relevant for mDNS.
Sat Dec 30 20:31:06 2023 daemon.info avahi-daemon[4233]: Interface eth0.IPv6 no longer relevant for mDNS.
Sat Dec 30 20:31:06 2023 daemon.info avahi-daemon[4233]: Leaving mDNS multicast group on interface eth0.IPv6 with address .
Sat Dec 30 20:31:06 2023 daemon.info avahi-daemon[4233]: Withdrawing address record for on eth0.
Sat Dec 30 20:31:06 2023 daemon.notice netifd: Interface ‘wan’ is enabled
Sat Dec 30 20:31:06 2023 kern.info kernel: [31610.339531] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sat Dec 30 20:31:06 2023 user.notice firewall: Reloading firewall due to ifdown of wan ()
Sat Dec 30 20:31:25 2023 daemon.notice netifd: Network device ‘eth0’ link is up
Sat Dec 30 20:31:25 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity
Sat Dec 30 20:31:25 2023 daemon.notice netifd: Interface ‘wan’ is setting up now
Sat Dec 30 20:31:25 2023 kern.info kernel: [31629.263783] nss-dp 3a001000.dp1 eth0: PHY Link up speed: 100
Sat Dec 30 20:31:25 2023 kern.info kernel: [31629.264083] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sat Dec 30 20:31:25 2023 daemon.notice netifd: wan (18741): udhcpc: started, v1.33.2
Sat Dec 30 20:31:25 2023 daemon.notice netifd: wan (18741): udhcpc: sending discover
Sat Dec 30 20:31:25 2023 daemon.notice netifd: wan (18741): udhcpc: sending select for
Sat Dec 30 20:31:25 2023 daemon.notice netifd: wan (18741): udhcpc: lease of obtained, lease time 86400
Sat Dec 30 20:31:25 2023 daemon.info avahi-daemon[4233]: Joining mDNS multicast group on interface eth0.IPv4 with address .
Sat Dec 30 20:31:25 2023 daemon.info avahi-daemon[4233]: New relevant interface eth0.IPv4 for mDNS.
Sat Dec 30 20:31:25 2023 daemon.info avahi-daemon[4233]: Registering new address record for on eth0.IPv4.
Sat Dec 30 20:31:25 2023 daemon.notice netifd: Interface ‘wan’ is now up
Sat Dec 30 20:31:25 2023 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Sat Dec 30 20:31:26 2023 daemon.info avahi-daemon[4233]: Joining mDNS multicast group on interface eth0.IPv6 with address .
Sat Dec 30 20:31:26 2023 daemon.info avahi-daemon[4233]: New relevant interface eth0.IPv6 for mDNS.
Sat Dec 30 20:31:26 2023 daemon.info avahi-daemon[4233]: Registering new address record for on eth0.*.

I can’t figure out the issue, nor ISP is helpful.

Could you try to enable IPv6 on the Flint and try if there will be a connection then?

I just tested, enabling IPv6 via gui. Nothing changed.

Hi, it might be a compatibility issue between your ISP and the AX1800. Can you please tell me what your ISP is?

Or maybe your cable max speed 100mb?

ISP is just dhcp connection via RJ-45.
Technician does not found any issues but suggested it could be cat5e (4-pairs, 100mbit) cable 30 meters lengths.
I retested with cisco unmanaged switch between Flint and ISP (instead of R7000), still in that configuration connection work just fine.
:thinking:

Yes, it is 100mbps, cat5e cable