Beryl AX Losing Link on Both Interfaces

I have a Beryl AX (GL-MT3000), running Firmware Version 4.8.1, which I use whenever I travel. On my most recent trip trip, it started regularly (every 30 seconds to 5 Minutes) losing link on both the LAN and WAN interfaces when handling any traffic (it doesn’t lose link when idle). It recovers in a few seconds. If anyone has any insight, here is an applicable example system log entry:

Mon Apr 13 14:44:00 2026 kern.info kernel: [ 499.548891] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Mon Apr 13 14:44:00 2026 daemon.notice netifd: Network device 'eth0' link is down
Mon Apr 13 14:44:00 2026 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Apr 13 14:44:00 2026 daemon.notice netifd: wan (4904): udhcpc: received SIGTERM
Mon Apr 13 14:44:00 2026 daemon.notice netifd: wan (4904): udhcpc: unicasting a release of 172.23.50.6 to 172.23.50.1
Mon Apr 13 14:44:00 2026 daemon.notice netifd: wan (4904): udhcpc: sending release
Mon Apr 13 14:44:00 2026 daemon.notice netifd: wan (4904): udhcpc: entering released state
Mon Apr 13 14:44:00 2026 daemon.notice netifd: wan (4904): Command failed: Permission denied
Mon Apr 13 14:44:00 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Mon Apr 13 14:44:00 2026 daemon.notice netifd: Interface 'wan' is now down
Mon Apr 13 14:44:00 2026 daemon.info avahi-daemon[6116]: Withdrawing address record for 172.23.50.6 on eth0.
Mon Apr 13 14:44:00 2026 daemon.info avahi-daemon[6116]: Leaving mDNS multicast group on interface eth0.IPv4 with address 172.23.50.6.
Mon Apr 13 14:44:00 2026 daemon.info avahi-daemon[6116]: Interface eth0.IPv4 no longer relevant for mDNS.
Mon Apr 13 14:44:00 2026 daemon.info avahi-daemon[6116]: Interface eth0.IPv6 no longer relevant for mDNS.
Mon Apr 13 14:44:00 2026 daemon.info avahi-daemon[6116]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe54:e307.
Mon Apr 13 14:44:00 2026 daemon.info avahi-daemon[6116]: Withdrawing address record for fe80::9683:c4ff:fe54:e307 on eth0.
Mon Apr 13 14:44:00 2026 daemon.notice netifd: Interface 'wan' is disabled
Mon Apr 13 14:44:00 2026 kern.info kernel: [ 499.692818] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Mon Apr 13 14:44:00 2026 daemon.notice netifd: Interface 'wan' is enabled
Mon Apr 13 14:44:00 2026 daemon.warn dnsmasq[10824]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Apr 13 14:44:00 2026 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Mon Apr 13 14:44:00 2026 kern.debug kernel: [ 499.861517] kmwan: Delete node:wan
Mon Apr 13 14:44:00 2026 user.notice firewall: Reloading firewall due to ifdown of wan ()
Mon Apr 13 14:44:03 2026 kern.info kernel: [ 502.780493] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Mon Apr 13 14:44:03 2026 kern.info kernel: [ 502.788952] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mon Apr 13 14:44:03 2026 daemon.notice netifd: Network device 'eth0' link is up
Mon Apr 13 14:44:03 2026 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Apr 13 14:44:03 2026 daemon.notice netifd: Interface 'wan' is setting up now
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): udhcpc: started, v1.33.2
Mon Apr 13 14:44:03 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): udhcpc: sending discover
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): udhcpc: sending select for 172.23.50.6
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): udhcpc: lease of 172.23.50.6 obtained, lease time 86400
Mon Apr 13 14:44:03 2026 daemon.info avahi-daemon[6116]: Joining mDNS multicast group on interface eth0.IPv4 with address 172.23.50.6.
Mon Apr 13 14:44:03 2026 daemon.info avahi-daemon[6116]: New relevant interface eth0.IPv4 for mDNS.
Mon Apr 13 14:44:03 2026 daemon.info avahi-daemon[6116]: Registering new address record for 172.23.50.6 on eth0.IPv4.
Mon Apr 13 14:44:03 2026 daemon.notice netifd: Interface 'wan' is now up
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: using only locally-known addresses for domain test
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: using only locally-known addresses for domain onion
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: using only locally-known addresses for domain localhost
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: using only locally-known addresses for domain local
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: using only locally-known addresses for domain invalid
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: using only locally-known addresses for domain bind
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: using only locally-known addresses for domain lan
Mon Apr 13 14:44:03 2026 daemon.info dnsmasq[10824]: using nameserver 100.64.0.7#53
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): PING 172.23.50.1 (172.23.50.1): 56 data bytes
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): 64 bytes from 172.23.50.1: seq=0 ttl=64 time=2.402 ms
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167):
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): --- 172.23.50.1 ping statistics ---
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): 1 packets transmitted, 1 packets received, 0% packet loss
Mon Apr 13 14:44:03 2026 daemon.notice netifd: wan (17167): round-trip min/avg/max = 2.402/2.402/2.402 ms
Mon Apr 13 14:44:03 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Mon Apr 13 14:44:03 2026 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wan", "netdev": "eth0", "track_mode": "force", "addr_type": 4, "force_ip": "172.23.50.6", "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Mon Apr 13 14:44:03 2026 kern.debug kernel: [ 503.201480] [add_dev_config 319]add node success. iface:wan, dev:eth0, ifindex:2
Mon Apr 13 14:44:03 2026 daemon.info gl-repeater[2610]: (repeater.lua:1741) interface wan status offline
Mon Apr 13 14:44:04 2026 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Mon Apr 13 14:44:04 2026 daemon.info avahi-daemon[6116]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe54:e307.
Mon Apr 13 14:44:04 2026 daemon.info avahi-daemon[6116]: New relevant interface eth0.IPv6 for mDNS.
Mon Apr 13 14:44:04 2026 daemon.info avahi-daemon[6116]: Registering new address record for fe80::9683:c4ff:fe54:e307 on eth0.*.
Mon Apr 13 14:44:07 2026 daemon.info gl-repeater[2610]: (repeater.lua:1741) interface wan status online

Any insight would be appreciated.

What kind of connections do you plug in each port? Like, what is the WAN and what is the LAN side?

Thanks for responding, admon.

The LAN side is a Linux laptop. The WAN side I tried connecting to 2 different devices: (1) my brother's ISP router (when on my trip) and (2) a Cisco switch, itself connected to my OPNsense firewall (to see if behavior was different with a different topology). I should add that I have connected the Beryl similarly in the past, without the issue manifesting itself.

Might there be some IP network overlap on both ports maybe?

Not probable. Beryl LAN subnet is 192.168.8.0/24; Beryl WAN subnet is (currently) 172.23.50.0/29.