Every time I set static IP address I can't access the router - 1st time set up of a dumb AP - Cudy WR3000 v1

[Chris3]

Hello everybody,

I’ve just flashed OpenWrt 25 onto my Cudy WR3000 v1 using this guide here. For the last couple of hours I have been trying to set it up as an AP using this guide.

Long story short, every time I change the IP address of the LAN Interface and Apply & Save, the changes aren’t applied. I have to wait the whole 90 second periodand then the changes are reverted – once or twice I was asked whether I want to reroll or keep the settings – I managed to click the red button Apply Unchecked a few times - still, the router was inaccessible both via the old 192.168.1.1 IP as well as the new ones.

I do connect via a cable and I am plugged into the LAN slot, not the WAN one. I tried many different configurations – changing the IP address only; changing the IP and disabling DHCP at the same time, changing the IP first and then trying to disable DHCP, disabling firewall/dsqmask and changing the IP address – even tried changing the settings via SSH - these and many more.

I’m using a laptop without a rj45 port so I have to rely on a usb hub, I’m using Fedora KDE. I even grabbed a spare laptop with a built in LAN slot, as well as a windows machine – still, no results. I tried to change my IP address on my laptops, didn’t work as well. Used AI a bit and it’s been unhelpful, tried ssh to change the settings – lost the connection after chaning the IP and wasn’t able to access the router at all.

The bottom line, however, is that I am forever stuck – after changing its IP, I can’t access my router via 192.168.1.1 nor via the new IP (say 192.168.1.10). I tried to leave the router in DHCP mode and connected it to my main router too. I tried to hook my new AP onto my main router (Cudy WR3000H with OpenWRT 24 on board) too, once I even was able to access the internet via Wifi without being able to access the new AP’s settings.

Not sure if it’s worth mentioning, but when rolling the official Cudy firmware, before flashing OpenWRT I did use this machine as an AP and following the manufacturers steps while setting it up– it created a subnetwork with a 192.168.10.X address and I wasn’t able to change it into the one from my original network 192.168.1.X – there weren’t any double NAT problems though, it worked fine. Still, I decided to go with OpenWrt and it’s been, well, painful.

Tl;dr Can’t set up a static IP address while creating an AP using Cudy Wr3000 v1

Thanks in advance for your help, I've been at it for two days and it's been really frustrating. Here are some screenshots of things I've changed.

[lleachii]

@Chris3

the router was inaccessible both via the old 192.168.1.1 IP as well as the new ones.

Did you change the IP on your client to be in the new subnet you changed your router to (or allow DHCP to assign the new address to it)?

@Chris3

Cudy Wr3000 v1

3000P, H, which model of the WR3000?

Edit:

@Chris3

Here are some screenshots of things I've changed.

I see the IP is in the same subnet. Did you try browsing to http://192.168.1.222 after changing and applying the IP (withn 90 seconds)?

Also, I see that you didn't add the network range of /24 to the end of your edit.

[Chris3]

Hello, thanks for your quick reply.

@lleachii

3000P, H, which model of the WR3000?

My setup is as following:
FTTH - ONT - Cudy WR3000H /w OpenWRT 24 (PPPOE Vlan 35 connection) - numerous dumb APs incl. Cudy WR3000 v1 (no H, no P, no S, no E, plain WR3000.

@lleachii

Did you change the IP on your client to be in the new subnet you changed your router to (or allow DHCP to assign the new address to it)?

My main router (the one that replaces ISP's gear) is 192.168.1.1 and all my other dumb APs and devices are also in the range of 192.168.1.10-192.168.1.199. I do have a few dhcp reservations in 192.168.1.200-205 range.

Here are some photos of the router, the adapter that I used and the port I used, which is not WAN.

@lleachii

I see the IP is in the same subnet. Did you try browsing to http://192.168.1.222 after changing and applying the IP (withn 90 seconds)?

I'm not sure, thought it was necessary for me to wait before the changes were applied so I just waited. I did try that a few times as well, after asking AI for help, and obviously it didn't work.

@lleachii

Also, I see that you didn't add the network range of /24 to the end of your edit.

Didn't know it was required, before making my WR3000h my main router, I used it as a dumb AP and it was enough just to add the IP without thge /24 range.

I'll try that, thanks.

[Chris3]

@lleachii

I see the IP is in the same subnet. Did you try browsing to http://192.168.1.222 after changing and applying the IP (withn 90 seconds)?

That, my friend, was the solution to the problem! Thank you very much @lleachii - it worked and I managed to connect to the new IP within 90 seconds, now the dumb AP finally works! Thanks a lot, you've made my morning. Cheers.