[Solved] Unable to access my AP after initial config

My router is a Luma and I installed Openwrt 23.05.

Post sysupgrade and installing Luci, I was able to access it and wanted to change the settings to a dumb AP.

I put in a static IP (192.168.55.4), the dns and gateway as my router (another luma is 192.168.55.1).

Post this, after reboot I am unable to access the AP via Luci. I have connected the AP to my main router via LAN port.

I have rebooted the main router and the openwrt router multiple times.

Using Fing I see the router as 192.168.55.4 but ping or browsing or ssh doesnt work. The ip address seems to change to a random ip when i dont connect to the main router at that time I am able to ping but still no Luci.ssh.

One of the possible issues seems to be that Luma seems to reserve the first 20 ips for its mesh network.

I am sure I didnt do the settings correctly but anyway to get access now other than using serial connections as its a pain to remove the backpanel (again).

Are you certain you entered the address properly when you changed the config? What does fing say about the device at 192.168.55.4? And does it fail to see it if you unplug the AP?

We can try to troubleshoot the situation itself, or you can jump to recovery methods.

The fastest way to recover is likely just to use failsafe mode and reset to defaults. Or, you could view the config and try to fix whatever is wrong.

https://openwrt.org/docs/guide-user/troubleshooting/failsafe_and_factory_reset

1 Like

I am quite sure I entered something wrong.

Fing seems to show the device even when its powered off. So i delete the device and do a refresh, now it doesnt show.

Did a reset (I thought the reset will take me back to my old luma settings, but looks like it went to base openwrt. I can now access luci @192.168.1.1

Thanks for the response. Although I have to figure what i did wrong and hopefully i will read the instructions better :slight_smile:

This might be useful:

https://openwrt.org/faq/change_lan_ip

1 Like

And in the meantime, since you've now got access to the device again, I would imagine the immediate issue is solved.

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks! :slight_smile:

2 Likes

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.