Wifi pulling bad IP when connecting to router

This could very much be a router issue on my end, but posting here in case it helps anyone else.

After updating to the most recent firmware, V1.15, my maslow is connecting to my wifi but pulling a bad IP address. It is setting itself to the IP of the router itself. xxx.xxx.x.1. Obviously this won’t work as that’s the DNS address for the router.

Has anyone else had this issue? Any idea how to fix it? I’m considering pulling the yaml and setting a static IP manually.

JimB wrote:

This could very much be a router issue on my end, but posting here in case it helps anyone else.

After updating to the most recent firmware, V1.15, my maslow is connecting to my wifi but pulling a bad IP address. It is setting itself to the IP of the router itself. xxx.xxx.x.1. Obviously this won¢t work as that¢s the DNS address for the router.

are you sure it’s connecting to your router and not failing to connect and
therefor setting itself up as the AP?

Has anyone else had this issue? Any idea how to fix it? I¢m considering pulling the yaml and setting a static IP manually.

the static IP is set in the nvram, not the yaml file.

David Lang

Yeah I noticed that.

I’m pretty sure it was connecting to the router properly. don’t know why it was trying to use the routers gateway as its IP.

I did the trick of turning off my router to get the Maslow AP to show up again. Then I went into the FluidNC settings in the GUI and set it to static IP there. Powered the network router back on, then powered on Maslow and I’m back in.

2 Likes