OpenWrt support for Xiaomi AX3000T

First get ssh access, then you can run dmesg command and investigate log.
Or filter like here:

root@XiaoQiang:~# dmesg -r | grep AN8855
root@XiaoQiang:~# dmesg -r | grep MT7531AE
[ 0.669158] mt753x gsw@0: Switch is MediaTek MT7531AE rev 1

See the first command with AN8855 returned nothing because I don't have AN8855, but the second command returned Switch is MediaTek MT7531AE

Another method is to disassemble and look at the switch chip, but what is the point?

Also run dmesg | grep nand to understand what flash is installed, not everything is supported, mine says GigaDevice which means it is ESMT and it is supported. I've read that foresee flash is not supported.
Also, flash chip is visible through perforation on the bottom of the router, my clearly says ESMT.

3 Likes

I dont have any major issues w 5G either. It does have some occasional speed drops and few packet loss in some games but otherwise its very solid.

Thank you very much for your help! I can say that I was lucky twice.

root@XiaoQiang:~# dmesg -r | grep MT7531AE
root@XiaoQiang:~# dmesg -r | grep AN8855
<6>[ 1.553513] an8855 gsw@0: AN8855 Driver Version=1.0.3
<6>[ 1.864061] an8855 gsw@0: Switch is Airoha AN8855 rev 1
root@XiaoQiang:~# dmesg | grep nand
[ 0.718871] spi-nand spi0.0: Foresee SPI NAND was found.

I'll put this router aside for a while and wait for new firmware.

I made my build available on github with all patches that im including for full transparency:

@victor186 I added the patch they were talking about in the issue u opened, would u mind trying this build and report back if it makes a difference?

I also have 2 AX3000T with Airoha AN8855. I am using @dimfish version from 15-10-2024.
My configuration is 1 main router with pppoe connected to Huawei gpon router configured as bridge. I have few vlans on it.
Second router is dumb access point by lan.
I have configured wifi roaming and i can say that i have better wifi performance on main router - wifi speed 2.4 and 5 GHz. 5ghz around 400/500, 2.4 150/500.
Dumb access point 5ghz 170/500, 2.4 110/500.
I am mesouring it near to router. It is worse than i have originally on Huawei router but pros overweight cons.
Everything else works great. I do not have any internet drops on wifi and lan, on any vlan. Ping also is ok.
The main router has been running for over 2 weeks, the dumb one for 3 days. They have many restarts. I have connected mamy different devices to each vlan for example server, print server, mamy mobile phones, pcs, tvs, reapeater, iot devices. It was a good deal.

I've just received my AX3000T from AliExpress and thankfully it's an older version. So I powered up the device, connected it to a laptop and started XMiR patcher. Was trying to get SSH enabled. It tells me to setup the device before it can work. I tried in bridge mode, but then I could reach it and had to reset it. WiFi default GW is 192.168.1.1 is the same as my flint2. What a pain.

Can anyone suggest the best way to get XMir patcher working without having to go through the whole setup process via app or web interface?

Thanks.

"Configure device" - this is the initial setup of the Chinese web interface with entering a password of just...
and 192.168.31.1 for the router by default.

1 Like

~ 6 reboots blocked...
without the built-in counter reset patch, the version without (OpenWrt U-Boot layout) is not suitable for use, since very few people will read and apply the patches themselves, mostly they will brick.

The 5G AP on mine just disappears after a while. It's not quite ready to be released into the wild yet.

My disappeared because DFS, turned out radar is working around. (DFS-RADAR-DETECTED)

Tue Nov 26 03:33:12 2024 daemon.notice hostapd: phy1-ap0: DFS-RADAR-DETECTED freq=5540 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5530 cf2=0
Tue Nov 26 03:33:12 2024 daemon.notice hostapd: dfs_downgrade_bandwidth: no DFS channels left, waiting for NOP to finish
Tue Nov 26 03:33:12 2024 daemon.notice hostapd: phy1-ap0: AP-DISABLED
2 Likes

I have the same messages in my log. Thanks for the heads up. I'm not sure if there's any radars near though, could it be it's not reading it correctly?

I don't know how accurate detection is, maybe some interference can trigger it too. I don't know about any radars nearby too, I installed a router in the attic a few days ago, worked fine. The problem has coincided with highly increased military activity in my area (Shahed 136 around). I thought all this DFS stuff is just theoretical, but apparently, radars use those frequencies to detect targets. Hi from Ukraine:)

Just use non-DFS channel, and everything will be fine.

P.S. My observation: if the channel is non-DFS the 5GHz network starts being visible right after reboot, if the channel is DFS it takes much longer to start working, apparently because it looks for radar, it may give a false impression that the 5GHz in the router is unreliable.

3 Likes

U need to apply this after installing, no issues at all:
https://openwrt.org/inbox/toh/xiaomi/ax3000t#basic_configuration

I'll go and check the channels that are free and switch to something less likely to have interference.

Wishing you wisdom, strength and stamina from Nederland.

1 Like

Underneath the script it states -

Don't run this command if the issue doesn't affect you, and your router keeps its settings after 6 reboots!

Is there a simple command (I seem to remember seeing one further up in the thread) that will tell you how many reboots it may have had?
Until you get to 6 reboots how would you know if it is affected..........until you reboot and get a brick......so doesn't it make sense to run that script anyhow?

Me personally I disagree with the bottom part, i think u should always do it first thing if ur using the stock bootloader no matter what. Seen quite a few ppl fall victim to this issue.
You can use fw_printenv and look for the same variable, the value will be the number of reboots.

I didn't even know it needed to be changed, this is from the router that I was using for half a year. flag_try_sys1_failed=116, is there gonna be a surprise when/if it overflows?

flag_boot_rootfs=0
flag_boot_success=1
flag_boot_type=2
flag_last_success=1
flag_ota_reboot=0
flag_try_sys1_failed=116
flag_try_sys2_failed=8

if it's more than 6 and it's not dead, then nothing will happen to it. The same problem exists on the AX3200 (AX6S), but there direct editing of the bootloader with several commands solves the problem forever.

there are recommendations for this router too
ssh

fw_setenv boot_fw1 "run boot_rd_img;bootm"
fw_setenv flag_try_sys1_failed 0
fw_setenv flag_try_sys2_failed 0
fw_setenv flag_boot_rootfs 0
fw_setenv flag_boot_success 1
fw_setenv flag_last_success 0

but I haven't tried it because it's possible to insert commands directly into the firmware.

1 Like

Probably not, i assume its an older version of their bootloader that doesnt care about the value. Thats why the wiki is written the way it is i assume, but theres no harm in setting it to 0.

2 Likes

Added patching the necessary nvram variables in todays build.

3 Likes