I naively ordered a xiaomi AX3000T on aliexpress lured by the low price and openwrt-friendly chipset (happy owner of a zyxel ax6000 filogic 830 router)
I got lucky to receive the chinese version (I don't know which nand has tho), so after a couple happy days with the stock fw, I decided to upgrade to openwrt 24.10. Install went smooth as glass, but then when I started to ssh I noticed an unbearable lag, and I was like, 50cm away from the router.
At this point, wifi seems to be almost broken/unusable, 2Mbit/s at most on a Gbit network. Wired access is pretty stable. Is there a known problem with the wifi driver here or am I missing something? Also, 2.4GHz seems not to go up at all.
Did you keep settings when you upgraded?
And/or
What changes did you make to the default config?
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
1 Like
Well, yes (i think, it was pretty straightforward). Didn't lose any mac address or driver config. I also switched to my wifi locale but still. Wi-Fi 2.4GHz shows in the frequency spectrum when doing bands scanning however is not shown as physically on in LuCi (it shows -/-92dBm) and by other devices. Wi-Fi 5GHz is received at high strength and low noise. I can't get the issue. Does it make sense to upgrade via luci to a snapshot build?
{
"kernel": "6.6.73",
"hostname": "OpenWrt",
"system": "ARMv8 Processor rev 4",
"model": "Xiaomi Mi Router AX3000T",
"board_name": "xiaomi,mi-router-ax3000t",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.0",
"revision": "r28427-6df0e3d02a",
"target": "mediatek/filogic",
"description": "OpenWrt 24.10.0 r28427-6df0e3d02a",
"builddate": "1738624177"
}
}
config is fine, i just checked, there's just a bunch of ip route config I added myself so it's very long. But I'm pretty sure it's not the issue here, since it's the same since first install. The ping at 50cm is horrendous
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=20.528 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.570 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=735.620 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=355.907 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=104.761 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=269.372 ms
Request timeout for icmp_seq 8
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=469.761 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=470.737 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=230.307 ms
Request timeout for icmp_seq 12
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1595.075 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=591.782 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1098.393 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=93.169 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=41.338 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=471.682 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=574.626 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=81.436 ms
^C
--- 192.168.1.1 ping statistics ---
20 packets transmitted, 17 packets received, 15.0% packet loss
round-trip min/avg/max/stddev = 2.570/423.945/1595.075/410.331 ms
In case someone else will read this thread in the future, as of now, switching to ImmortalWRT (24.10.2 (r33247-467867283bb9)) via luci sysupgrade did NOT resolve the wifi issue.
The vendor configs are not compatible with official openwrt. Therefore, it is likely your problem is caused by the fact that you didn’t reset to defaults during the upgrade (i.e. uncheck the keep settings box when you run sysupgrade).
Try resetting to defaults and see if that solves your problem.
Or. Better yet, download 24.10.2 which was recently released and upgrade. When you do that, make sure that you do not keep settings by unchecking the box or using the -n argument you use the cli.
There is one other thing to look out for. If this is cascaded behind another router, you may have a subnet conflict (specifically if the upstream uses 192.168.1.0/24). If that is the case, change the lan subnet of this device to a non-overlapping one.
Downgraded to stock fw rd03_1.0.47 via miwifirepair/TFTP then reinstalled openwrt 24.10.2. This solved the issue, thanks a lot!