I just flashed a new RT-AX53U with 23.05.2 and I don#t see any issue with WAN nor WLAN so far.
What was the exact issue, I should look for?
Does it just start after running a few hours?
I'll keep an eye on it.
One thing I noticed was, that it only shows 32 MB of available flash instead of the 128 MB it is supposed to have.
edit: after a restart WAN was not connected anymore and I figured out it would not connect back unless I would connect a switch in between the Asus and the upstream fibre router.
edit2: this is when directly connected to the upstream router:
Tue Dec 26 18:35:18 2023 daemon.notice netifd: Network device 'wan' link is up
Tue Dec 26 18:35:18 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Dec 26 18:35:18 2023 daemon.notice netifd: Interface 'wan' is setting up now
Tue Dec 26 18:35:18 2023 kern.info kernel: [ 1323.710222] mtk_soc_eth 1e100000.ethernet wan: Link is Up - 100Mbps/Full - flow control off
Tue Dec 26 18:35:18 2023 daemon.notice netifd: Interface 'wan6' has link connectivity
Tue Dec 26 18:35:18 2023 daemon.notice netifd: Interface 'wan6' is setting up now
Tue Dec 26 18:35:18 2023 daemon.notice netifd: wan (22012): udhcpc: started, v1.36.1
Tue Dec 26 18:35:19 2023 daemon.notice netifd: wan (22012): udhcpc: broadcasting discover
Tue Dec 26 18:35:19 2023 kern.info kernel: [ 1324.750133] mtk_soc_eth 1e100000.ethernet wan: Link is Down
Tue Dec 26 18:35:19 2023 daemon.notice netifd: Network device 'wan' link is down
Tue Dec 26 18:35:19 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Dec 26 18:35:19 2023 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Tue Dec 26 18:35:19 2023 daemon.notice netifd: wan (22012): udhcpc: received SIGTERM
Tue Dec 26 18:35:20 2023 daemon.notice netifd: wan (22012): udhcpc: entering released state
Tue Dec 26 18:35:20 2023 daemon.notice netifd: wan (22012): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Tue Dec 26 18:35:20 2023 daemon.notice netifd: Interface 'wan' is now down
Tue Dec 26 18:35:20 2023 daemon.notice netifd: Interface 'wan6' is now down
And this via the switch:
Tue Dec 26 18:32:28 2023 daemon.notice netifd: Network device 'wan' link is up
Tue Dec 26 18:32:28 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Dec 26 18:32:28 2023 daemon.notice netifd: Interface 'wan' is setting up now
Tue Dec 26 18:32:28 2023 kern.info kernel: [ 1153.151183] mtk_soc_eth 1e100000.ethernet wan: Link is Up - 1Gbps/Full - flow control off
Tue Dec 26 18:32:28 2023 daemon.notice netifd: Interface 'wan6' has link connectivity
Tue Dec 26 18:32:28 2023 daemon.notice netifd: Interface 'wan6' is setting up now
Tue Dec 26 18:32:28 2023 daemon.notice netifd: wan (19114): udhcpc: started, v1.36.1
Tue Dec 26 18:32:28 2023 daemon.notice netifd: wan (19114): udhcpc: broadcasting discover
Tue Dec 26 18:32:31 2023 daemon.notice netifd: wan (19114): udhcpc: broadcasting discover
Tue Dec 26 18:32:34 2023 daemon.notice netifd: wan (19114): udhcpc: broadcasting discover
Tue Dec 26 18:32:34 2023 daemon.notice netifd: wan (19114): udhcpc: broadcasting select for 192.168.178.31, server 192.168.178.1
Tue Dec 26 18:32:35 2023 daemon.notice netifd: wan (19114): udhcpc: lease of 192.168.178.31 obtained from 192.168.178.1, lease time 864000
Tue Dec 26 18:32:35 2023 daemon.notice netifd: Interface 'wan' is now up
I wonder if it has sth. to do with the upsteam router only having a 100 Mbit port?