I have one EAP that is connected via Ethernet from the PoE injector to a switch, but will either be isolated, or stuck in the adoption process. It is currently attempting to adopt but with an ip address of 192.168.0.254. I was previously able to get it to adopt with a 192.168.1.xxx address, but once I was off-site, it became isolated, then at some point tried to re-adopt with the wrong ip address.

Here's my basic network layout:

Modem > Router > Jetstream > OC200

Router > Primary Ubiquiti NanoStation (PtMP)

Remote NanoStation > switch > EAP

There are a total of 4 remote NanoStations, each with at least one EAP and multiple PoE cameras. They all work properly except this particular one. For whatever reason it is getting a .0.254 address, and will not adopt. When I previously got it to connect and adopt with a proper ip, it was immediately after I logged into the NanoStation and opened the subnet by changing it to 255.255.0.0 (primarily for the cameras, which are using 192.168.2.xxx addresses, but the byproduct was that the EAP started working, at least until after I had left the site).