Bro - get your parents/grandparents/cousins windows pc to help.
1 Like
I had already tried everything. I had an unmodified Windows 11 device from a friend. We even tried Windows 10. The router is deaf. Nobody can tell me that this is normal.
I'm already looking at what materials I need for the serial port, then I'll try using it.
A quick question for the experts:
I found a tool like this, is it something?
In terms of marketing, the device seems to have been made for me. I can even send future routers to near death with my magic hands and revive them, at least that's what I think.
you should find something cheaper at your local Amazon, if you search for usb ttl 3.3v.
Is a Raspberry Pi Pico (or Pico 2) with headers better than an expensive ready-made product, also in terms of future projects? If I have read this correctly somewhere, then this small board can be used almost universally, from reading and flashing a BIOS to this serial interface of my router, provided I have all the necessary materials at hand. Is that correct? Unfortunately, I have no idea.
The vanilla RPi got them too, with pins pre-soldered.
Hi, I have a similar situation. Two months ago, I installed a custom snapshot image (kernel 6.12.x, created with local imagebuilder) on my Asus AX53U. I have several VLANs, including a management VLAN for SSH logins. The WAN port is a trunk to the main router – the AX53U acts as a dumb AP, Wi-Fi works, connected devices receive addresses from the appropriate pools from the main router, everything seemed fine. I usually update the firmware every few weeks, so some time later I also took a look at this AP (also because I remembered that the reboot command didn't work when I was configuring the AP and I wanted to check if new builds would fix it). The first indication that something was wrong was that I couldn't log in with the configuration transferred from the previous AP. I decided to check the configuration in failsafe mode. I did a cold reboot, pressing reset button and looking at the leds, it entered failsafe mode, but I still couldn't log in via SSH (I changed the PC's IP addresses/masks accordingly). Since AX53U was in use and everything worked except ssh logging I left it without updating the firmware. A month later, I bought a Cudy WR3000P v1 to replace the AX53U. I configured it from scratch, and to my surprise, after replacing the AX53U, I couldn't log in via SSH on the trunk port (WAN). I was using a TP-Link UE300 USB adapter under Windows 11 (VLAN ID set to management). I was about to disassemble it and connect a UART... fortunately, I had an additional access port for the management VLAN, and I was able to log in – the configuration seemed correct. I decided to try it under Linux Manjaro. I set management vlan id on the ue300’s interface using the ip command, and I was able to log in through the trunk port (WAN), so it seems to be a Windows issue.
Are you saying failsafe mode was not reachable with button? There is OEM-TFTP mode if you hold button before LED blinks fast....
Judging by the LEDs, the AX53U entered failsafe mode, but I was unable to connect to it via Putty (failsafe ip 192.168.1.1/24 port 22) from any PC (I tried two PCs running Windows 11, both connected directly to the LAN1 port with a Cat5e cable).
In normal operation, on both the Asus AX53U and the Cudy WR3000P v1, I had the WAN ports configured as trunks for VLANs (mgmt, work, guest, etc.). If I wanted to log in, I set the Tp-link UE300 vlan id = mgmt id and connected via putty to the router's WAN port. These two models, the AX53U and WR3000P v1, have now stopped accepting connections with Windows 11. Under Linux, this mgmt VLAN connection works and I can log in to router.
I have 4 dumb APs snapshot build 32566 at home (2x Redmi AX6000, Flint 2, and Asus Tuf AX6000) with trunk WAN configuration (mgmt, home, guest, iot, etc.) and I can log in to each one from Windows 11.
So something is wrong with the vlan support on both the AX53U and WR3000P or it is Windows 11 issue.
Ok, water ran away already, you can no longer recover past conditions.
A missing dhcp (you dont get IP, have to set manially)
B missing drop bear (absent any info from you it may spend extra minute generating host keys)
C wrong internñl switch config (sometimes only first or last lan port works)