On an irregular schedule, I am seeing the following on an OpenWrt One with 24.10.5
Mon Jan 26 01:19:52 2026 kern.info kernel: [143072.078182] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Mon Jan 26 01:19:52 2026 daemon.notice netifd: Network device 'eth0' link is down
Mon Jan 26 01:19:52 2026 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Jan 26 01:19:52 2026 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Mon Jan 26 01:19:52 2026 daemon.notice netifd: wan (6316): udhcpc: received SIGTERM
Mon Jan 26 01:19:52 2026 daemon.notice netifd: wan (6316): udhcpc: entering released state
Mon Jan 26 01:19:52 2026 daemon.notice netifd: wan (6316): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Jan 26 01:19:52 2026 daemon.notice netifd: Interface 'wan' is now down
Mon Jan 26 01:19:53 2026 daemon.notice netifd: Interface 'wan6' is now down
Mon Jan 26 01:19:59 2026 daemon.notice netifd: Network device 'eth0' link is up
Mon Jan 26 01:19:59 2026 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Jan 26 01:19:59 2026 daemon.notice netifd: Interface 'wan' is setting up now
Mon Jan 26 01:19:59 2026 daemon.notice netifd: Interface 'wan6' has link connectivity
Mon Jan 26 01:19:59 2026 daemon.notice netifd: Interface 'wan6' is setting up now
What can I do to debug this?
I am happy to re-flash the device or to do whatever debugging is needed. I just need it to be reliable, I can’t have it dropping out while working from home.
On the other end of eth0 is an Australian fibre NTD which supplies an Ethernet cable out and no diagnostics other than an LED