23.05.0 Update breaks WAN - RT-AX53U/1800U

[Filu]

Same issue as I tried once with latest release for 22.03.5-rc4
It seems that issue comes back with every update.
I got back to Stable 22.03.5 release again.

[Michael.Uray]

I can confim, I noticed the same WAN interface problems with version 23.05.0.
No problems with 22.03.5.

This is the original post which the OP is referring to, but it got automatically closed:

ASUS RT-AX1800U (AX53U) WAN port issue on SNAPSHOT, Wireless Tab Missing on 22.03.5

Hi, I recently bought ASUS RT-AX1800U (AX53U), which seemed to be perfect for batman-adv mesh network. So I made image through OpenWRT Firmware Selector with not to much changes ( 22.03.5 ). wpad-basic-wolfssl changed to wpad-basic-openssl, luci, luci-ssl, batman-adv. After flashing image into device it works fine and all... But Wireless "Tab/Option" is missing. I tried to find help here on forum, but there was no resolution. Can't upgrade packages too, for some reason. [screenshot1] Als…

[r7eyes]

Anyone know if 23.05.2 fixed this? I don't see any mention of it on the changelog

[eFfeM]

I don't know exactly what the original issue was but I just installed a virgin RT-AX1800U with OpenWrt 23.05.2.
Under network I have a Wireless page. It shows me the radios and a list of associated stations.

I picked up the image from https://downloads.openwrt.org/releases/23.05.2/targets/ramips/mt7621/ (the wiki page of the device still lists 23.05.0 as the latest version)

Note that I did not modify the image in any way. I just flashed the factory image using mtd-write on my new AX1800U

[r7eyes]

Does the WAN port work? That's what the wiki page said was broken.

[eFfeM]

Does the WAN port work? That's what the wiki page said was broken.

Yes it does. I connected the router through the wan port and connected my phone to the wireless. The phone gets the connection and can use it.
I also connected my laptop to the lan port and the laptop also gets an active internet connection. Actually that is what I am using to type this.

Note that I used the factory image as provided. I did not use the firmware selector or so

[Mccg]

I am also using it as a fiber modem. Can I switch from version 22.03.5 to version 23.05.2 smoothly, Is Wi-Fi problem solved?

[x-daemon]

yesterday, after I upgraded it to 23.05.2, the internet stopped working. then I downgraded to 22.03.5 and it worked again. I use pppoe:
pppd[3325]: Remote message: Too many sessions^J
pppd[3325]: PAP authentication failed
pppd[3325]: Connection terminated.

[r7eyes]

After flashing 23.05.2, the WAN port and Wifi tab seems to be both working fine on my device.

However, the network performance is horrendous for some reason. I can barely get 150Mbps down on my 500Mbps connection with speedtest.net, and only ~350Mbps on local gigabit crossing VLANs using iperf3. Even when I reset the settings and configured it as a dumb AP/switch connected to a Rpi4 router, I still get similar degraded speeds for the local connection.

Downgrading to 22.03.5 doesn't have these issues, at least as a dumb AP/switch. Getting ~450Mbps with WAN and ~950Mbps on local gigabit across VLANs, so I guess I'll stay on 22.03.5 for this device.

[hbswn]

@eFfeM

I don't know exactly what the original issue was . . .

The previous 23.5.0 didn't show the Wireless menu, but 23.5.2 fixed that.

I do not have the 160MHz bandwidth option in "Operating frequency", but that didn't work anyway (on 22.03.5 ).

Model: ASUS RT-AX53U
Architecture: MediaTek MT7621 ver:1 eco:3
Target Platform: ramips/mt7621
Firmware Version: OpenWrt 23.05.2 r23630-842932a63d / LuCI openwrt-23.05 branch git-23.306.39416-c86c256
Kernel Version: 5.15.137

I use this router as a local (via the WAN-port) connected as a client to a Fritzbox doing the DSL connection.

[x-daemon]

after I upgraded to 22.03.6, the connection to the internet takes 6 minutes. maybe I didn't wait long enough? after I upgraded to 23.05.2 it connects to the internet, too.

[boki]

Has anyone tried a clean flash of 23.05.2 with mtd-write?
23.05.0 did not work last few times I tried, wondering if .2 fixed anything?
Thanks!
-- Boki

[asehsdfb]

Hi! I'd also love to know if 23.05.2 is okay to flash.

[boki]

I tried a week or so ago… did not work, unfortunately

[asehsdfb]

Thank you!

[asehsdfb]

Is this issue present in recent snapshots?

[fireburner]

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?

[molnaratt]

Any update on that topic? Do snapshots fixed this issue?

[Mccg]

halo. im OpenWrt 22.03.5 ax53u user. may i update to 22.03.6 via Attended Sysupgrade without any problems?

[linuxuser]

If you do not need WAN in any case, I recommend to use 23.05.2. Beamforming works a lot better then, as I found out here:

ASUS RT-AX53U: Beamforming configuration

Interesting thing. I was on 22.03.6 because of mentioned WAN-problems, but for the moment I do not need WAN. So I tried 23.05.2 root@AX53U-S1:~# ubus call system board { "kernel": "5.15.137", "hostname": "AX53U-S1", "system": "MediaTek MT7621 ver:1 eco:3", "model": "ASUS RT-AX53U", "board_name": "asus,rt-ax53u", "rootfs_type": "squashfs", "release": { "distribution": "OpenWrt", "version": "23.05.2", "revision": "r23630-842932a63d", "target": "ramips/mt7621", "description": "Ope…