Flint 2: interfaces randomly going down

Technical Support for Routers
1

Hey everyone. I'm trying to figure out the problem: once in 20-30 hours what I hid in the spoiler happens. I'm currently using 24.10-rc4, tried 23.05.5 - same story. The only thing is that I haven't tried the firmware from GL.iNet, but it's on an older version which, as I understand, doesn't support Sing-box which is vital to me. And others with newer firmware seem to have no problems. If possible I would like to stay on a newer version. Has anyone experienced this?

What I don't understand is why lan3 is present in the logs when I have nothing connected to it at all.

Log

Tue Dec 31 03:35:35 2024 daemon.notice netifd: Network device 'lan1' link is down
Tue Dec 31 03:35:35 2024 kern.info kernel: [ 927.283226] br-lan: port 1(lan1) entered disabled state
Tue Dec 31 03:35:35 2024 kern.info kernel: [ 927.283331] mt7530-mdio mdio-bus:1f lan1: Link is Down
Tue Dec 31 03:35:52 2024 kern.info kernel: [ 943.611807] mt7530-mdio mdio-bus:1f lan3: Link is Up - 1Gbps/Full - flow control rx/tx
Tue Dec 31 03:35:52 2024 kern.info kernel: [ 943.611860] br-lan: port 3(lan3) entered blocking state
Tue Dec 31 03:35:52 2024 kern.info kernel: [ 943.624963] br-lan: port 3(lan3) entered forwarding state
Tue Dec 31 03:35:52 2024 daemon.notice netifd: Network device 'lan3' link is up
Tue Dec 31 03:35:53 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.232 f4:39:09:28:9a:6d
Tue Dec 31 03:35:53 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.232 f4:39:09:28:9a:6d win
Tue Dec 31 03:35:53 2024 daemon.notice netifd: Network device 'eth1' link is down
Tue Dec 31 03:35:53 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Dec 31 03:35:53 2024 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Tue Dec 31 03:35:53 2024 kern.info kernel: [ 945.370233] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Tue Dec 31 03:35:53 2024 daemon.notice netifd: wan (4546): udhcpc: received SIGTERM
Tue Dec 31 03:35:53 2024 daemon.notice netifd: wan (4546): udhcpc: unicasting a release of [REDACTED] to [REDACTED]
Tue Dec 31 03:35:53 2024 daemon.notice netifd: wan (4546): udhcpc: sending release
Tue Dec 31 03:35:53 2024 daemon.notice netifd: wan (4546): udhcpc: entering released state
Tue Dec 31 03:35:53 2024 daemon.notice netifd: wan (4546): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Tue Dec 31 03:35:53 2024 daemon.notice netifd: Interface 'wan' is now down
Tue Dec 31 03:35:54 2024 daemon.notice netifd: Interface 'wan6' is now down

2

Since you are using plain OpenWrt the question would be better inside the OpenWrt forum than here.

If running OpenWrt 24 is necessary for you, you could try the op24 version of the GL firmware which is more up to date: GL.iNet download center

Keep in mind to reset all settings when switching firmwares.

3

Try a different Ethernet cable. These devices like quality connections.

4

Or try with a better power cable.

If its still doing that, it can be a issue with netifd but i don't think this is a OpenWrt issue, i believe they already fixed it there.

Do you use any exotic configuration?

Then please post the contents of:

/etc/config/network (remove vpn keys, and mac addresses)