I just tried ssh connection to my router, but it isn't letting me proceed since I have added a password for the root account.
I am on a Windows 11 laptop, how can I supply my password while connecting via SSH?
Open Windows command prompt console and type the following command:
ssh root@192.168.1.1
=> you will then be prompted to enter the password.
Or just use Putty to establish SSH connection.
Putty worked! It indeed has ESMT.
root@OpenWrt:~# dmesg | grep nand
[ 0.772426] spi-nand spi0.0: ESMT SPI NAND was found.
[ 0.777496] spi-nand spi0.0: 128 MiB, block size: 128 KiB, page size: 2048, OOB size: 64
Slightly off-topic, but do you know if AX3000T (RD03) supports Mesh configuration with another router (different company and model) running OpenWRT? If there's capability for it, how can I check?
Thank you.
yes, it should be capable: https://openwrt.org/docs/guide-user/network/wifi/mesh/start
1 Like
- Remove all mentions of "SSH exploit", it's not a SSH exploit.
- Change the
OpenWrt Installation Methodto eitherAPI RCE (misystem/arn_switch)orAPI RCE (xqsystem/start_binding), depending on firmware. - Merge the arn_switch script within Installation/Flash instructions, as the URL path is the only thing that differs between them. Better yet, merge both scripts into one:
./script.sh misystem/xqsystem token. - Make mention of XMiR-Patcher as an easier method for first time flashing (for initramfs).
- Remove any flashing mentions or instructions from
Downgrading stock firmware. Leave this section with only firmware downgrade instructions as flashing instructions are covered in another section already.
2 Likes
Thank you, much appreciated! 
I'll reach out you in private messages if there are any further questions before the updated version is released.
and
You can also use XMiR-Patcher to start flashing OpenWrt U-Boot. You can immediately flash the blah-blah-blah-ubootmod-initramfs-factory.ubi file with it, bypassing all the steps for flashing up to this point.
You don't have to downgrade the firmware version on 1.0.47. XMiR-Patcher can already work with all current firmware versions, even with those routers that are not supported by OpenWrt (Xiaomi). It is better to suggest this as a last resort, since there are many cases of bricking routers with firmware 1.0.84 after such a downgrade.
"Strongly recommended" ))) the author of XMiR-Patcher finally fixes the problem of creating a full backup copy of routers, which is currently impossible and ends with an error and reboot of the router, which leads to a repeat of all previously performed actions, i.e. starting the procedure from the very beginning.
Anyone also have a problem with IPv6 not routing correctly?
SNAPSHOT:
ping -6 kernel.org no routing
ping -6 kernel.org -I wan no routing
ping -6 kernel.org -I <any of my IPv6 addresses> routes
This is basically the same configuration from my old Archer C6 V2 (US) on 23.05.03, but somehow is not working correctly with the AX3000T.
EDIT: No idea what's up. I can ping my local devices from the router just fine (both ULA and non-local addresses assigned from the delegated prefix).
root@router1:~# ip -f inet6 route list
default from ... via fe80::... dev wan metric 512
default from .../64 via fe80::... dev wan metric 512
default from .../64 via fe80::... dev wan metric 512
default from .../64 via fe80::... dev wan metric 512
All of them have a correct entry.
EDIT: tcpdump: unsupported DSA tag: mtk
Ugh...
EDIT: Might be a problem with my ISP's configuration (as usual). Of the three assigned addresses, only one routes (addresses generated from the delegated prefix also route).
>>> import socket
>>> s = socket.socket(socket.AF_INET6, socket.SOCK_DGRAM, 0)
>>> s.connect(("kernel.org", 1))
>>> s.getsockname()
('implicit bind is to one of the bad/non-routed addresses', 59664, 0, 0)
My prefix/addresses changed due to the change of MAC addresses when replacing the routers.
EDIT: Yeah, it's my ISP, it was just a coincidence that this happened exactly when I switched my routers. These idiots managed to break IPv6, even when connected directly through a Linux or Windows desktop PC.
Good night, everyone.
I am new to router firmware and interacting with openwrt firmware in general.
3 days ago I bought this router Xiaomi AX3000T global version R23 with firmware 1.0.31 from our network of computer stores.
Since the device is based on Winbond NAND, I read that it can only be flashed with Snapshot versions.
With the help of xmir-patcher-main I filled it with firmware
xiaomi_mi-router-ax3000t-initramfs-factory.ubi - from https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/.
The firmware was uploaded, SSH access worked, installed luci and tried to update to stable version 23.05.5. The error was uploaded but it stopped booting at all.
I restored the firmware (miwifi_rd23_firmware_153e1_1.0.49_INT.bin) via MIWIFIRepairTool.
Again through xmir-patcher-main poured into it firmware xiaomi_mi-router-ax3000t-initramfs-factory.ubi , installed luci in it and through web-interface rolled this version of xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin into it from the same folder.
The problem is that at first it was reset to default settings without luci installed. Then after a few hours it stopped doing this, and started to keep the settings after saving, rebooting and in principle power off.
But I encountered that I save the settings, reboot it a few times, and after about 6-8 reboots it resets to the factory defaults of openwrt again. Is there something more stable for this version?
or I'm doing something wrong.
I also read that it might have something to do with
root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 4.3M 4.3M 0 100% /rom
tmpfs 116.8M 212.0K 116.6M 0% /tmp
/dev/ubi0_1 61.4M 156.0K 58.1M 0% /overlay
overlayfs:/overlay 61.4M 156.0K 58.1M 0% /
tmpfs 512.0K 0 512.0K 0% /dev
with what it shows /dev/root 4.3M 4.3M 0 100% /rom
Can you tell me which way to dig )
Root cause explained here .
I understand the cause,
but the solution is fw_setenv flag_try_sys1_failed 0 into /etc/rc.local ?
After setting it to 0 it stops counting ? Or does it have to be updated every time ?
In most cases it helps resolve the issue with configs resetting after 6 reboots on the stock Xiaomi bootloader. (However, a small number of users reported that it causes the router to soft-brick).
I am not sure about RD23, but on RD03, once I flashed OpenWrt's U-Boot, the flags were gone and I've rebooted it quite a lot without problems, even turned the mesh button into a "hold for 3s to reboot" button, as the device doesn't have a power button.
After several reboots, the router not booting up. An orange LED is on only. DCHP service not works. May be need to run some commands after FW install?
Have you tried manual dhcp setting on your network adapter?
And which additional packages are installed (e.g. stubby, dns-over-https,...)
Or try to reset the settings (with the help reset button).
Yes, I'm tried yo set static ip. Reset button not works. The only the "dns-over-https" package was installed.
Same problem as AX3200, but it (AX3200) doesn't have custom bootloader, so to prevent it from freezing after installation you need either custom bootloader or boot counter reset commands which are given above.
MIWIFIRepairTool.x86 and all over again.
Is this manual suitable for the RD23 (Winbond)?
I installed the openwrt factory firmware onto my ax3000t CN (stock firmware 1.0.47) using xmir-patcher and now the router is bricked with the red light and am not receiving an internet connection. What did I do wrong and how can I debrick the router?
EDIT: Found out my router has a “winbond” chip. How do I debrick my router?
Yes, but still via MIWIFIRepairTool.x86 it is easier, but on the page you gave, I did not find any mentions. This is the same TFTP method, only the utility does everything itself, except assigning an address to the computer's network card.