-
the controller is running on a totally random IP
The Pi is running on a random IP, meaning that it receives it's IP via DHCP.
You should login to the Pi and configure a static IP for it. Then once it's stable, login to whatever your Ubiquiti DHCP server is and configure a static IP map for the Pi that matches what you've just done.
After that... you're good to go.
-
The Pi is running on a random IP, meaning that it receives it's IP via DHCP.
DHCP is set up on 192.168.1.0/24 to have a range from 192.168.1.38 to 192.168.1.243
Looking a bit further, I think it might be because the pi is not able to get an address from DHCP, and is giving itself an address. Which I never knew was a thing.
You should login to the Pi and configure a static IP for it. Then once it's stable, login to whatever your Ubiquiti DHCP server is and configure a static IP map for the Pi that matches what you've just done.
I'm trying that now - but even with the IP known, I can't ssh into the Pi. And I have no idea where my bluetooth keyboard went...
I'll try mount the Pi SD card somewhere else & mangle a few conf files.
After that... you're good to go.
Good to find another way to stop things from working, you mean.
And to think, all I was trying to do was replace a wall power socket.
Problem #199 with my wifi
I have a unifi controller (running on a pi) that had been working fine until mid-morning, when I had to shut down all of the power sockets downstairs.
When I brought the power backup, the controller is running on a totally random IP, on a completely different address block 169.244.0.0/16
My router is set up with:
eth0 - WAN - cable modem
eth1 - LAN1 - 192.168.1.1/24
eth2 - LAN2 - 192.168.2.1/24
I did have to have the controller on LAN1 to adopt the APs, and change the inform address manually, but the worked fine when I moved it back onto LAN2
Even if I switch the pi back onto LAN1, it is taking an IP on 169.244.0.0/16
I have the Pi's MAC set up in the router to have a static IP on LAN1 / 2
Any ideas about what I'm doing wrong?