Yes, if you have a throughput issue then you may want to resolve that in the stock firmware first, but I have had really good wireless performance from the latest snapshot builds of openwrt. I would not bother with the stock firmware, personally.
2 Likes
Ok, so the ARP issue was due to OPNsense bridge getting all confused where to forward the ARP reply to it seems. As soon as I removed the bridge there and used a single port instead, it all went away.
@jav Thank you so much for all your suggestions.
1 Like
Thank you, as i understood its a worth to try openwrt...I hope i will find an insturction for idiots like me 
And i don't know tbh how to resolve it in the stock Redmi AX6000 firmware, i changed bandwidth, channel, and the best i have found i did describe in the message above (350download speed and 470 upload speed) on an iphone.
Thank you, Anon.
Guys, one more question please. Is it a possible to return (in future) firmware to stock of Redmi AX6000 firmware after me will do OpenWrt? In a case Wi-Fi performance will be worse then now?
There're two OpenWrt flavors to choose from: stock and u-boot mod. The stock one allows returning to the original firmware. In the second one, in theory it could be done too, but no one has tried yet.
Please check the wiki page for details:
1 Like
Thank you, Jav. 
1 Like
hello there,
Any expected date for releasing the official version of OpenWrt for Redmi AX6000 ?
also, is the snapshot version (u-boot mod) completely stable with no issues so far ?
Not sure what you mean with official version?
This version is very stable with very good performance.
If you want a build with Luci and other stuff pre-installed go for X-WRT. Works very well too.
Not tried u-boot yet, as reverting to stock is more complicated. But this is probably stable as well.
snapshot (Openwrt U-boot layout) is very stable, installed it since this feature is available to AX6000, never had any problem up to date.
The only problem I've had was with Xiaomi's U-Boot, after a hard reset on Openwrt (made some mistake in configuration, and Openwrt stopped respond), it went back to XiaoMi's firmware and lost ssh, telnet access.
2 Likes
You don’t need X-WRT for LuCI, just build from source and enable the package
2 Likes
Looks like a number of commits today that might have some impact on Redmi AX6000: https://github.com/openwrt/openwrt/commits/master?since=2023-03-02&until=2023-03-02
1 Like
Hello guys:
How's it going?
I had a Redmi AX6000 router working correctly with the stock layout, until I updated the firmware via LuCi.
Since I updated the router, the LEDs are always blue, I can't get the IP address because the LAN connection is restarting in a loop.
Could you please help me to recover the router?
Thank you in advance.
Greetings
You can use the Xiaomi MIWIFIRepairTool, I think it is just a telnet recovery but works for me!
Thank you so much for answering my question so fast.
Do you know any manual to use the repair tool?
Self-response:
I use this manual: Xiaomi Mi Router 4A Gigabit Edition (R4AG/R4A Gigabit) -- fully supported and flashable with OpenWRTInvasion - #747 by Zorro
Thank you so much.
hello there ladies and gentlmen,
I'm not expert with openwrt, but the question is,
can I move to immortalwrt FW from current openwrt FW thru Luci interface ?
after testing openwrt
version (Snapshot r22191-f6a7ce2501 / Luci master git-23.039.28596-41e9b8d)
kernal 5.15.96
and Immortalwrt
version (Immortalwrt 18.06-5.4-SNAPSHOT r11814-ef0c86bdb0 / Luci branch (git-22.323.17670-f9380b5))
kernal 5.4.224
Immortalwrt customized seems more powerful in wifi signal strength since it is working in (OFDMA+MU-MIMO) mode, exactly like redmi stock firmware signal strength.
Hi,
I'm a newbie on OpenWRT and trying to install it on my new Redmi AX6000 router.
My router comes with 1.0.64 FW and before starting the steps, I downgraded it to 1.0.48 FW
I followed all steps on the article and got bootloader loop after executing this command:
sysupgrade -n /tmp/squashfs-sysupgrade.bin
My router is not turning on and stuck in bootloader loop.
I checked it via serial terminal and got this log:
03:07:01.038 -> Boot failure detected on both systems
03:07:01.038 -> Reading from 0x0 to 0x5f7fdd8c, size 0x4 ... OK
03:07:01.038 -> Saving Environment to MTD... Erasing on MTD device 'nmbm0'... OK
03:07:01.074 -> Writing to MTD device 'nmbm0'... OK
03:07:01.074 -> OK
03:07:01.074 -> Booting System 0
03:07:01.074 -> ubi0: attaching mtd9
03:07:01.184 -> ubi0: scanning is finished
03:07:01.184 -> ubi0: attached mtd9 (name "ubi", size 30 MiB)
03:07:01.184 -> ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
03:07:01.221 -> ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
03:07:01.221 -> ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
03:07:01.221 -> ubi0: good PEBs: 240, bad PEBs: 0, corrupted PEBs: 0
03:07:01.221 -> ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
03:07:01.221 -> ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1233335465
03:07:01.221 -> ubi0: available PEBs: 185, total reserved PEBs: 55, PEBs reserved for bad PEB handling: 19
03:07:01.264 -> Reading from volume 'kernel' to 0x46000000, size 0x0 ... OK
03:07:01.651 -> ## Loading kernel from FIT Image at 46000000 ...
03:07:01.651 -> Using 'config-1' configuration
03:07:01.651 -> Trying 'kernel-1' kernel subimage
03:07:01.651 -> Description: ARM64 OpenWrt Linux-5.15.98
03:07:01.651 -> Type: Kernel Image
03:07:01.651 -> Compression: lzma compressed
03:07:01.651 -> Data Start: 0x460000e8
03:07:01.651 -> Data Size: 3945112 Bytes = 3.8 MiB
03:07:01.651 -> Architecture: AArch64
03:07:01.651 -> OS: Linux
03:07:01.651 -> Load Address: 0x48000000
03:07:01.651 -> Entry Point: 0x48000000
03:07:01.651 -> Hash algo: crc32
03:07:01.689 -> Hash value: 22a5ee1e
03:07:01.689 -> Hash algo: sha1
03:07:01.689 -> Hash value: c311e964f1140662f74c9eb85f483807f50815da
03:07:01.689 -> Verifying Hash Integrity ... crc32+ sha1+ OK
03:07:01.728 -> ## Loading fdt from FIT Image at 46000000 ...
03:07:01.728 -> Using 'config-1' configuration
03:07:01.728 -> Trying 'fdt-1' fdt subimage
03:07:01.728 -> Description: ARM64 OpenWrt xiaomi_redmi-router-ax6000-stock device tree blob
03:07:01.728 -> Type: Flat Device Tree
03:07:01.728 -> Compression: uncompressed
03:07:01.775 -> Data Start: 0x463c34d0
03:07:01.775 -> Data Size: 32768 Bytes = 32 KiB
03:07:01.775 -> Architecture: AArch64
03:07:01.775 -> Hash algo: crc32
03:07:01.775 -> Hash value: b1b77c32
03:07:01.775 -> Hash algo: sha1
03:07:01.775 -> Hash value: ab3e4e1eb6d5675b7477266c63401e48abc57c62
03:07:01.775 -> Verifying Hash Integrity ... crc32+ sha1+ OK
03:07:01.775 -> Booting using the fdt blob at 0x463c34d0
03:07:01.775 -> Uncompressing Kernel Image
03:07:02.299 -> ERROR: Failed to allocate 0xb000 bytes below 0x6c000000.
03:07:02.299 -> Failed using fdt_high value for Device TreeFDT creation failed!
03:07:02.406 -> resetting ...
Full log can be seen from here: https://pastebin.com/83qGr2tm
How can I resolve this problem?
@soxrok2212 might have idea about what it is...
Hi @qrizzz, I might have similar issue, how did you resolve eventually?
Any guide how to connect and use the UART?
Hi @robsdesk, seems I have similar problem, can you share specific details how to flash with UART?
How to find the right pins, which image to burn and how. Thanks