Weird disconnects intermittently on XE-3000

Hello, running a xe-3000 Puli currently on Ethernet connected to a DOCSIS modem, with cellular as backup. Running version 4.8.3.

I am getting an intermittent reset of the wan - this was primarily happening when on cellular as primary, but now I’ve seen it on both.

it happens over the course of 3-5 seconds, just long enough for my connections to drop and require a reconnect. Do the below logs suggest anything to anyone? I tried a factory reset and reinstall, but im scratching my head here;

Fri May 29 14:59:13 2026 kern.info kernel: [64992.888357] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Fri May 29 14:59:13 2026 daemon.notice netifd: Network device 'eth0' link is down
Fri May 29 14:59:13 2026 daemon.notice netifd: Interface 'wan' has link connectivity loss
Fri May 29 14:59:13 2026 daemon.notice netifd: wan (5885): udhcpc: received SIGTERM
Fri May 29 14:59:13 2026 daemon.notice netifd: wan (5885): udhcpc: unicasting a release of 50.158.106.157 to 172.19.41.120
Fri May 29 14:59:13 2026 daemon.notice netifd: wan (5885): udhcpc: sending release
Fri May 29 14:59:13 2026 daemon.notice netifd: wan (5885): udhcpc: entering released state
Fri May 29 14:59:13 2026 daemon.notice netifd: wan (5885): Command failed: Permission denied
Fri May 29 14:59:13 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Fri May 29 14:59:13 2026 daemon.notice netifd: Interface 'wan' is now down
Fri May 29 14:59:13 2026 daemon.info gl-repeater[3284]: (repeater.lua:1895) interface wan down
Fri May 29 14:59:13 2026 daemon.info gl-repeater[3284]: (repeater.lua:1593) switch in 3 seconds...
Fri May 29 14:59:13 2026 daemon.info avahi-daemon[13164]: Withdrawing address record for 50.158.106.157 on eth0.
Fri May 29 14:59:13 2026 daemon.info avahi-daemon[13164]: Leaving mDNS multicast group on interface eth0.IPv4 with address 50.158.106.157.
Fri May 29 14:59:13 2026 daemon.info avahi-daemon[13164]: Interface eth0.IPv4 no longer relevant for mDNS.
Fri May 29 14:59:13 2026 daemon.notice netifd: Interface 'wan' is disabled
Fri May 29 14:59:13 2026 kern.info kernel: [64993.055034] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Fri May 29 14:59:13 2026 daemon.notice netifd: Interface 'wan' is enabled
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: reading /tmp/resolv.conf.d/resolv.conf.auto
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain test
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain onion
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain localhost
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain local
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain invalid
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain bind
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain lan
Fri May 29 14:59:13 2026 daemon.info dnsmasq[19988]: using nameserver 192.0.0.30#53
Fri May 29 14:59:13 2026 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Fri May 29 14:59:13 2026 kern.debug kernel: [64993.247532] kmwan: Delete node:wan
Fri May 29 14:59:14 2026 user.notice firewall: Reloading firewall due to ifdown of wan ()
Fri May 29 14:59:16 2026 daemon.info gl-repeater[3284]: (repeater.lua:1519) no saved network
Fri May 29 14:59:17 2026 daemon.notice netifd: Network device 'eth0' link is up
Fri May 29 14:59:17 2026 daemon.notice netifd: Interface 'wan' has link connectivity
Fri May 29 14:59:17 2026 daemon.notice netifd: Interface 'wan' is setting up now
Fri May 29 14:59:17 2026 kern.info kernel: [64997.143309] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Fri May 29 14:59:17 2026 daemon.notice netifd: wan (6130): udhcpc: started, v1.33.2
Fri May 29 14:59:17 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Fri May 29 14:59:17 2026 daemon.notice netifd: wan (6130): udhcpc: sending discover
Fri May 29 14:59:18 2026 daemon.notice netifd: wan (6130): udhcpc: sending select for 50.158.106.157
Fri May 29 14:59:18 2026 daemon.notice netifd: wan (6130): udhcpc: lease of 50.158.106.157 obtained, lease time 86400
Fri May 29 14:59:18 2026 daemon.info avahi-daemon[13164]: Joining mDNS multicast group on interface eth0.IPv4 with address 50.158.106.157.
Fri May 29 14:59:18 2026 daemon.info avahi-daemon[13164]: New relevant interface eth0.IPv4 for mDNS.
Fri May 29 14:59:18 2026 daemon.info avahi-daemon[13164]: Registering new address record for 50.158.106.157 on eth0.IPv4.
Fri May 29 14:59:18 2026 daemon.notice netifd: Interface 'wan' is now up
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: reading /tmp/resolv.conf.d/resolv.conf.auto
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain test
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain onion
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain localhost
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain local
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain invalid
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain bind
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using only locally-known addresses for domain lan
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using nameserver 68.105.28.11#53
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using nameserver 68.105.29.11#53
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using nameserver 68.105.28.12#53
Fri May 29 14:59:18 2026 daemon.info dnsmasq[19988]: using nameserver 192.0.0.30#53
Fri May 29 14:59:18 2026 daemon.notice netifd: wan (6130): PING 50.158.106.1 (50.158.106.1): 56 data bytes
Fri May 29 14:59:18 2026 daemon.notice netifd: wan (6130): 64 bytes from 50.158.106.1: seq=0 ttl=255 time=63.548 ms
Fri May 29 14:59:18 2026 daemon.notice netifd: wan (6130):
Fri May 29 14:59:18 2026 daemon.notice netifd: wan (6130): --- 50.158.106.1 ping statistics ---
Fri May 29 14:59:18 2026 daemon.notice netifd: wan (6130): 1 packets transmitted, 1 packets received, 0% packet loss
Fri May 29 14:59:18 2026 daemon.notice netifd: wan (6130): round-trip min/avg/max = 63.548/63.548/63.548 ms
Fri May 29 14:59:18 2026 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wan", "netdev": "eth0", "track_mode": "force", "addr_type": 4, "force_ip": "50.158.106.157", "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" } ] } ] } }
Fri May 29 14:59:18 2026 kern.debug kernel: [64997.667123] [add_dev_config 319]add node success. iface:wan, dev:eth0, ifindex:2
Fri May 29 14:59:18 2026 user.notice kmwan: config json str={ "op": 6, "data": { } }
Fri May 29 14:59:18 2026 daemon.info gl-repeater[3284]: (repeater.lua:1881) interface wan offline
Fri May 29 14:59:18 2026 daemon.info gl-repeater[3284]: (repeater.lua:1593) switch in 3 seconds...
Fri May 29 14:59:18 2026 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Fri May 29 14:59:21 2026 daemon.info gl-repeater[3284]: (repeater.lua:1519) no saved network
Fri May 29 14:59:22 2026 daemon.info gl-repeater[3284]: (repeater.lua:1881) interface wan online
Fri May 29 14:59:22 2026 daemon.info gl-repeater[3284]: (repeater.lua:1593) switch in 3 seconds...
Fri May 29 14:59:25 2026 daemon.info gl-repeater[3284]: (repeater.lua:1519) no saved network

Hi

Sorry for the delayed reply.

We reviewed the logs you provided and noticed that they appear to be truncated just before the WAN (eth0) disconnection event. As a result, we are unable to determine what caused the link to go down.

We recommend that the next time the issue occurs, you export the complete device logs and send them to us via private message for further analysis:

How to export logs:

How to send private messages: