I've got the same issues, the only way was to restore the router with the Mi WiFi app and then redo all the steps to get SSH access and flash OpenWrt from scratch.
Its because openwrt is installed on mtd13. You have to switch to mtd12. Sysupgrade works for me only on mtd12
Happy new year to everyone involved in this project!
I have ordered the RB5009UG+S+IN, but that will take quite some time to arrive.
I would be however interested in running the ax3600 as an ap for that router, perhaps with link aggregation to use the full potential of the wifi 6 band, which would be absolutely awesome.
Is this possible? Does openwrt allow this?
I have seen some posts about bonding, but would it work used the way I intend to or am I better off buying another ap device, although all things considered this is one of the best (and cheapest) router/ap on the market which has good wifi
If you have the xiaomi ax3600, it'll do fine, just give it a try - it'll be more than good enough until wifi 6e comes around (if you haven't bought anything yet, the dynalink or the slowly appearing filogic 830 options might be better). I would not expect benefits from bonding/ link aggregation though (might even be detrimental due to the current state of the ethernet/ switch drivers).
Finally got around to setting the network interface names to match what it says on the device for Xiaomi boards.
Since networking configs would break, compat version is enforced to only allow sysupgrading if config is not preserved.
I plan to follow-up with other boards as well, but I need somebody to match up the Dynalink, EAP102 and CAX1800.
Current mapping for Dynalink DL-WRX36 (let me know if you prefer it on the other thread):
|Label||OEM firmware||OpenWrt (2023-01-01-1522)|
Interfaces names between OEM and OpenWrt are aligned.
As for the "INTERNET" label, I'm not sure whether it should remain as "eth0", use "wan", or strictly follow the label and use "internet".
how? tried, but now the router has openwrt firmware to which the app can't connect
many thanks, this led me to the solution.
I got this envs:
flag_boot_rootfs=0 flag_boot_success=1 flag_boot_type=2 flag_last_success=1 flag_ota_reboot=0 flag_try_sys1_failed=0 flag_try_sys2_failed=1
It seems a boot (after install) failed earlier (
flag_try_sys2_failed=1) so the device doesn't boot from
after installing the factory image and clearing this env (
fw_setenv flag_try_sys2_failed 0) the ax3600 was able to boot from
mtd13 and has been working since.
ubiformat /dev/mtd13 -y -f /tmp/openwrt-ipq807x-generic-xiaomi _ax3600-squashfs-factory.ubi -s 2048 -O 2048 fw_setenv flag_boot_rootfs 1 fw_setenv flag_last_success 1 fw_setenv flag_try_sys2_failed 0 reboot
flag_boot_success=1 flag_boot_type=2 flag_last_success=1 flag_ota_reboot=0 flag_try_sys1_failed=0 flash_type=2 flag_boot_rootfs=1 flag_try_sys2_failed=0
Firmware Version OpenWrt SNAPSHOT r0-4203028 / LuCI Master git-22.361.69865-deed682
fortunately I had a config backup and could restore it.
HAPPY NEW YEAR TO ALL!
For the CAX1800: the device has only one Ethernet port, I'd call them just "lan".
Should I open a PR?
Great, I did not check the DTS before but then its easy.
No need for a PR, Il just add it along with other devices.
Do you know which ethN relates to which DP node?
If I remember correctly:
DP1 - eth0
DP2 - eth1
DP3 - eth2
DP4 - eth4
DP5 - eth5
only the DP regs are in an unusual order (highest to lowest)
I'm getting this (Dynalink DL-WRX36):
# ls -l /sys/class/net/eth*/device lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth0/device -> ../../../3a007000.dp1 lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth1/device -> ../../../3a001600.dp2 lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth2/device -> ../../../3a001400.dp3 lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth3/device -> ../../../3a001200.dp4 lrwxrwxrwx 1 root root 0 Jan 1 14:03 /sys/class/net/eth4/device -> ../../../3a001000.dp5
Thanks, that makes it easy.
I do plan to use the traditional OpenWrt wan/lan naming for it as well.
Using the printed ETHN makes no sense
Only EAP102 remains.
Hi, When I try to do sysupgrade version 63ba272 I receive a message "Image check failed:
Sun Jan 1 19:20:17 CET 2023 upgrade: The device is supported, but the config is incompatible to the new image (1.0->1.1). Please upgrade without keeping config (sysupgrade -n). Sun Jan 1 19:20:17 CET 2023 upgrade: Network interface names have changed Image check failed."
Should I use force upgrade?
PS Of course, it depends on me to keep the settings
The message is self explanatory.
Few posts above the author even notify about that change - Adding OpenWrt support for Xiaomi AX3600 - #9596 by robimarko
You're right, I read it before, but not carefully enough. Thx
I no longer have the device in my possession, but almost certain that for the EAP102, dp6 maps to eth0 (uplink-PoE) and dp5 maps to eth1 (LAN)
Thanks, will roll with that for now.
Flashing OpenWrt in both partition is a bit risky, i've always kept a partition with the stock firmware in cases like this so i can restore it with the MiWiFi recovery.
Just set the network adapter with: