GL-MT3000 WAN interface eth0 going up and down

I have a Netgear Nighthawk M6 (mr6150) connected to the Beryl AX / MT3000 WAN port. I was noticing the light blinking from time to time. I went into the Beryl and discovered the interface was going up and down about every 3 mins. Is this a negotiation issue? I have checked the cable of course. Any ideas?

Log output -
Sun May 28 17:01:36 2023 kern.info kernel: [ 1155.346129] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Sun May 28 17:01:36 2023 daemon.notice netifd: Network device ‘eth0’ link is down
Sun May 28 17:01:36 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity loss
Sun May 28 17:01:36 2023 daemon.notice netifd: Interface ‘wan’ is now down
Sun May 28 17:01:36 2023 daemon.info avahi-daemon[3628]: Withdrawing address record for 192.168.1.5 on eth0.
Sun May 28 17:01:36 2023 daemon.info avahi-daemon[3628]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.5.
Sun May 28 17:01:36 2023 daemon.notice netifd: Interface ‘wan’ is disabled
Sun May 28 17:01:36 2023 kern.info kernel: [ 1155.365201] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Sun May 28 17:01:36 2023 daemon.info avahi-daemon[3628]: Interface eth0.IPv4 no longer relevant for mDNS.
Sun May 28 17:01:36 2023 daemon.info avahi-daemon[3628]: Interface eth0.IPv6 no longer relevant for mDNS.
Sun May 28 17:01:36 2023 daemon.info avahi-daemon[3628]: Leaving mDNS multicast group on interface eth0.IPv6 with address
Sun May 28 17:01:36 2023 daemon.info avahi-daemon[3628]: Withdrawing address record for
Sun May 28 17:01:36 2023 daemon.notice netifd: Interface ‘wan’ is enabled
Sun May 28 17:01:36 2023 user.notice mwan3[3832]: Execute ifdown event on interface wan (unknown)
Sun May 28 17:01:36 2023 user.info mwan3track[30329]: Detect ifdown event on interface wan (eth0)
Sun May 28 17:01:36 2023 user.notice mwan3track[30329]: Interface wan (eth0) is offline
Sun May 28 17:01:36 2023 user.notice firewall: Reloading firewall due to ifdown of wan ()
Sun May 28 17:01:39 2023 kern.info kernel: [ 1158.445401] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Sun May 28 17:01:39 2023 kern.info kernel: [ 1158.453896] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sun May 28 17:01:39 2023 daemon.notice netifd: Network device ‘eth0’ link is up
Sun May 28 17:01:39 2023 daemon.notice netifd: Interface ‘wan’ has link connectivity
Sun May 28 17:01:39 2023 daemon.notice netifd: Interface ‘wan’ is setting up now
Sun May 28 17:01:39 2023 daemon.info avahi-daemon[3628]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.5.
Sun May 28 17:01:39 2023 daemon.info avahi-daemon[3628]: New relevant interface eth0.IPv4 for mDNS.
Sun May 28 17:01:39 2023 daemon.info avahi-daemon[3628]: Registering new address record for 192.168.1.5 on eth0.IPv4.
Sun May 28 17:01:39 2023 daemon.notice netifd: Interface ‘wan’ is now up
Sun May 28 17:01:39 2023 user.notice mwan3[4435]: Execute ifup event on interface wan (eth0)
Sun May 28 17:01:39 2023 user.notice mwan3[4435]: Starting tracker on interface wan (eth0)
Sun May 28 17:01:40 2023 user.notice mwan3track[30329]: Stopping mwan3track for interface “wan”
Sun May 28 17:01:41 2023 daemon.info avahi-daemon[3628]: Joining mDNS multicast group on interface eth0.IPv6 with address
Sun May 28 17:01:41 2023 daemon.info avahi-daemon[3628]: New relevant interface eth0.IPv6 for mDNS.
Sun May 28 17:01:41 2023 daemon.info avahi-daemon[3628]: Registering new address record for ipv6 on eth0.*.
Sun May 28 17:01:41 2023 user.info mwan3rtmon[7235]: Detect rtchange event.
Sun May 28 17:01:41 2023 user.notice firewall: Reloading firewall due to ifup of wan (eth0)

Usually this is due to a broken (or a low-quality) cable.
You can try connecting to a different port on the Nighthawk too.
Another option is to make the Beryl AX WAN port a LAN port and try locally with another device to test.

Make sure you’re on the latest firmware.

Thanks for this - I will try more cables and see if that fixes it. My nighthawk is the M6 hotspot and only has one port. I will switch the port and give it a shot.

I set the M6 ethernet speed to 100 Mbps and I have not had any issues. This seems to be an interface negation issue. I have tried a number of Cat6 cables with the same outcome. Is there a way to set the GLI WIAN interface speed manually?

You can also connect the computer to the M6. If there is no network disconnection, it may be a MT2500 problem. You can try to update the firmware. If it doesn’t work, it may be a port problem.

1 Like

It seems to work perfectly directly connected to my laptop. Perhaps it is a layer 1 problem with the port. Thanks for your reply.

Update on this issue - I exchanged this unit for a new one and all is well. I have been testing / running this for a couple days with no drops or issues. This appears to have been a physical issue with the port on my initial unit. Thanks to all who replied.

Hey! I am having the same issue. Did this happen only when under load or all the time?

It happens pretty much all the time. I would say every 3 to 5 minutes for me

Hello. I’ve the same problem. Beryl AX. eth0 goes down and up every about 3 minutes (irregularly). I’ve tried 3 different cables (including cables that worked fine with 1000 Mbps connections so far), didn’t help. I’ve the latest firmware (4.2.2). Upstream (ISP) is offering 1000 Mbps, not 2.5G.

If anybody has a solution, plese shout. I imagine limiting it to 100 Mbps using ethool (thanks for that tip!) could resolve the issue, but this is obviously not satisfactory if you are paying your ISP for more.

What eventually helped: swap “LAN” ↔ “WAN” ports. My internal LAN is gigabit, so both eth0 and eth1 in the router work at gigabit speed, but it still helped.

In case someone will want to know how to replace LAN with WAN: someone explained how to do that in the GL-MT3000: GL MT-2500 LAN and WAN port swap and switch option missing - #3 by K3rn3l_Ku5h

1 Like