Could anyone help me debrick Cudy WS3000S?
It’s been working fine on openwrt for about a month. Figured I would try the latest snapshot.
It booted fine on snapshot, changed the LAN IP from 192.168.1.1 to 192.168.10.1. openwrt didn’t want to take it, warning to apply anyway. I clicked apply anyway and … no DHCP. Also tried manually connecting to 192.168.10.1, doesn’t work. Used the reset button, didn’t reset. Used the reset pin, didn’t reset.
How could I try to debrick it?
That is not how IP addresses work.
Typo error in the title, it's WR3000S.
So you produce an error prone config and didn't bother to check what might be wrong at first but just hitting I'm feeling lucky today and then you wonder why stuff isn't working?
It might be good next time to as a very first step, make your self comfortable with the various recovery modes of your hardware.
If your ipv4 config is broken then just use IPv6 link local addresses to connect with ssh.
I prefer English 
. Openwrt forums somehow loads the English link in German … so copy paste from code:
https://www.cudy.com/blogs/faq/how-to-recovery-the-cudy-router-from-openwrt-firmware-to-cudy-official-firmware
Click on the link, page will auto-adapt to your language. I'm pretty confident that @frollic linked to the english page, but for some reason the text appears in german. I had this case myself already.
WTF, who marked frollics answer as the solution? Guys, can’t you read. The OP posted, that he changed the routers lan ip to 192.168.10.1 and then he tried to connect to the router on address 192.168.10.2.
OP did.
perhaps it's a typo ?
If it was a typo and he tried to connect to right address it would most likely have worked and if not then one should advise him on how to setup his client in order to connect to the correct lan ip of the router. Next time he attempts to change it, the same thing will happen.
There, corrected, thanks for pointing the typo.
By the way, has to do with the snapshots of last weekend. Had the same happen on a number of different brand routers. Snapshot lists LAN DHCP IP as x.x.x.x/24, whereas stable lists LAN DHCP IP as x.x.x.x When you change the LAN DHCP IP in snapshot to x.x.x.x it breaks. I didn’t do much more testing on it, reverted to stable now. Workweek.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
