23.05.0 Update breaks WAN - RT-AX53U/1800U

It seems like 23.05.2 is a hit-and-miss for some routers, My router seem to be stable so far but only time will tell...

I have been running on 23.05.0 without problems for 5 to 6 weeks.
But after a restart today nothing worked anymore. No wifi or LAN access. Not sure if WAN worked, unable to check.

Had to perform a firstboot. So running for some time does not indicate correct working.
I will have to reconfigure again. Considering reverting to 22.03.5 :thinking:

Does 22.03.06 works? Or it is just as crap as the other 23.05.xx versions? I wonder if there will be a fix for this issue soon.

2 Likes

Hi Everyone, any update on this issue? Can we expect a fix for 23.05.x track? Thanks in advance. 22.03.6 I have recently updated, and works fine, but 22.03 track EOL soon.

3 Likes

Hi Everyone, any update on this issue? Can we expect a fix for 23.05.x track? Thanks in advance. 22.03.6 I have recently updated, and works fine, but 22.03 track EOL soon.

Same, I am thinking to buy an ASUS RT-AX53U to run openwrt on it. Is any developer looking into this?

Is there someone with this router and some knowledge of internal workings of openwrt? I guess we could do a diff between 22.03.6 and 23.05.0 to figure out the root cause of the issue.

I have the RT-AX53U, Right now I'm on OpenWrt SNAPSHOT r25153-869df9ecdf / LuCI Master git-24.040.70477-23ebdb3, and have never seen the Wireless tab disappear, as outlined here.

I've been using this router for over a year with very few issues, but I do not use it for primarily WLAN, as I have APs for that (though DO run 2.4ghz for some IoT devices that side of the house...). It's been running flawlessly, I have gigabit internet through NBN here in Australia (1000/50), and it's been rock solid. Well worth the $65AUD.

I run snapshots (as that's what was supported at the time, stable is probably fine now) and update every month or when I remember.

I'm a bit confused, is this WAN (ie internet) or WLAN (Wireless LAN/WiFi)?

I see there is a mention of both, just confirming it's the Wireless tab missing, as it seems phy0-ap0 is missing as well from the ifconfig?

Are there logs in dmesg or something? I'd be happy to submit a bug / probably a bugfix if I can understand, and hopefully reproduce the issue.

edit: I just flashed 23.05.2, wiping settings as well, and can see the wireless tab.

Hi Everyone,
This is a very good router, and very fast via 1GBps Telekom Internet here in Hungary. As mentioned earlier currently running on 22.03.6, but EOL in April.
Is that possible to escalate this WAN (WIreless if any?) issues to OpenWrt developers to look into this, and to get a patch in next 23.05.x minor release?

2 Likes

You need to restart it a few times for it to not work. That is what i've gathered from the available information.

I just saw this thread now, and I also have had no issues with 23.05 on the RT-AX53U. I have been running and upgraded from 23.05.0 to 23.05.1 and 23.05.2

However, I use it simply as a dumb AP with 802.11q VLAN trunk through the WAN interface and to serve multiple SSIDs. Uplink is a 1Gb switch

Would pledge 25 € via PP for someone who fix this issue, i know it is not much but I am on a budget and this router is perfect otherwise.

EDIT: as it wasn't a bug money went to the project

2 Likes

hi @joshx1
I was trying to gather information based on forum entries regarding with this issue.
As far as I see it was came up only on 23.05.0 when someone was rebooted the router couple of times.
According to you findings, on Snapshot and 23.05.2 latest this issue was gone and router is kinda rock solid. Maybe some pkgs updates on Snapshot and on .2 this issue is fixed.
Can someone confirm it is safe to use with 23.05.2 latest? Any experience?
@joshx1 do you still running 23.05.2 for a while? any comments appreciated.

New topic is created for Developers:
https://forum.openwrt.org/t/23-05-x-wan-issue-rt-ax53u-1800u/190346/1

Please do not cross post.

If it hasn't already been done, feel free to submit a bug for this issue.

https://openwrt.org/bugs

Hi @psherman
Thanks for your feedback. As per your suggestion I reported a bug on GitHub:

UPDATE (not a bug and no need to fix it):

  • Bug ticket is closed, you can find the answer in the bug ticket (linked above), but lets summarize it:

Simply wan port is moved to separate netcard out of switch and old ethernet config is no longer valid. There is a warning to reset config when upgrading. Just get on with 23.05.2 , you will need to restore individual confs manually taking those in config backup as a reference.

  • Wiki page was modified by @humaita thanks for the support:

!Warning! Between versions 22.03.x and 23.05.x the WAN port was moved to a separate netcard out of the switch, so the old ethernet config is no longer valid and you need to reset the config in case of an upgrade. Just get on with 23.05.2 , you will need to restore individual confs manually taking those in config backup as a reference. https://github.com/openwrt/openwrt/issues/14801*

4 Likes

Awesome! Thanks @radiohead-lab for digging into this and bringing it to resolution!

Coincidentally I just received my ASUS RT-AX53U today! Will install latest stable version on it.

1 Like

I have been using Asus RT-AX1800U it is similar to ASUS RT-AX53U with the latest firmware 23.05.2 r23630-842932a63d for a few weeks now. No problems described above during this time did not occur, at the first stages of configuration router often rebooted but everything worked stably.

I am back at my parents place and tried again to replace the existing TP-Link with OpenWrt with the Asus RT-AX53U (23.05.2), but after a restart WAN still fails to come up again.
I will upgrade to 23.05.3 now and see if there is any difference.

Edit: upgraded to 23.05.3 and it is still the same.
This is a part from the log:

Mon Mar 25 12:57:02 2024 kern.info kernel: [   73.551268] mtk_soc_eth 1e100000.ethernet wan: Link is Up - 100Mbps/Full - flow control off
Mon Mar 25 12:57:02 2024 kern.info kernel: [   73.559712] IPv6: ADDRCONF(NETDEV_CHANGE): wan: link becomes ready
Mon Mar 25 12:57:02 2024 daemon.notice netifd: Network device 'wan' link is up
Mon Mar 25 12:57:02 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Mon Mar 25 12:57:02 2024 daemon.notice netifd: Interface 'wan' is setting up now
Mon Mar 25 12:57:02 2024 daemon.notice netifd: Interface 'wan6' has link connectivity
Mon Mar 25 12:57:02 2024 daemon.notice netifd: Interface 'wan6' is setting up now
Mon Mar 25 12:57:02 2024 daemon.notice netifd: wan (4604): udhcpc: started, v1.36.1
Mon Mar 25 12:57:02 2024 daemon.err odhcp6c[4605]: Failed to send RS (Address not available)
Mon Mar 25 12:57:02 2024 daemon.err odhcp6c[4605]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Mon Mar 25 12:57:02 2024 daemon.notice netifd: wan (4604): udhcpc: broadcasting discover
Mon Mar 25 12:57:03 2024 kern.info kernel: [   74.591401] mtk_soc_eth 1e100000.ethernet wan: Link is Down
Mon Mar 25 12:57:03 2024 daemon.notice netifd: Network device 'wan' link is down
Mon Mar 25 12:57:03 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Mon Mar 25 12:57:03 2024 daemon.err odhcp6c[4605]: Failed to send RS (Address not available)
Mon Mar 25 12:57:03 2024 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Mon Mar 25 12:57:03 2024 daemon.notice netifd: wan (4604): udhcpc: received SIGTERM
Mon Mar 25 12:57:03 2024 daemon.notice netifd: wan (4604): udhcpc: entering released state
Mon Mar 25 12:57:03 2024 daemon.notice netifd: wan (4604): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Mon Mar 25 12:57:03 2024 daemon.notice netifd: Interface 'wan' is now down
Mon Mar 25 12:57:03 2024 daemon.notice netifd: Interface 'wan6' is now down

When I connect a switch between the wall plug and the router, WAN comes up.

The wall plug is connected with an old cable (hence only 100 MBit/s) to the upstream router. As however both the TP-Link and the switch have no issues establishing a connection, I doubt the cable to be the problem here.

Hi Guys,
I have no issue with 23.05.2 on RT-AX53U/1800U at all. As we concluded the most important thing that you have to build up your configuration from scratch.
In case of any upgrade from 22.03.x you have to reset configuration and after successful upgrade configure it manually on cmdline or GUI. I think base 23.05.2 installation should be working fine as well from factory firmware image. I haven't tested that, only upgrade from 22.03.6.
My router is running w/o any issues on 23.05.2 since weeks. Configured VLANs, MWAN3, Fwknop, and enabled sw/hw firewall offload on fibre optic WAN (connected to Hungarian Telekom ONT 1Gbps running in bridge mode).
Works perfectly with tons of features configured.
Checked the latest 23.05.3 detailed changelog, but nothing specific regarding with this router, so 23.05.2 and .3 must be working fine.
/radiohead

1 Like

I had freshly installed mine with 23.05.2, so my issues are not due to old configs from the previous versions. Not sure however if my issue is the same as the original in this thread, connected to it or a completely different one.