1

Looking for a steer here.

We have unifi access points, which connect to a cloud controller.

They are configured locally with static IP and DNS settings in the 192.168.1.0/24 range.

After a network reconfiguration where the the DNS server and default gateway were changed to another range, we realised that we cannot not administer the access points from the cloud controller as they are no longer communicating.

I have set back up a small network internally with internet access and I can ping the devices, but I don’t have SSH details to access them.

However they still don’t seem to be reaching back out to the internet and I’m assuming it’s due to the fact they are now pointing to a non existent DNS server.

Any ideas how I could resolve this? Is there a way to locally access each device other than with SSH?

5 Spice ups
2

Can you not provide a dns server on the old ip? ofr example if you have setup a temporary network on the old range can the router not do the dns?

Or nat the old dns server ip to the new ip or 8.8.8.8

Otherwise ssh is the only way - but you can view the ssh password on the controller. got to controller > Settings > “Network Settings” > Device Authentication
the SSH username and password are then shown.

Use these details to ssh to the Aps and change the settings, or erase, re-adopt etc. See manual for the console interface commands.

3 Spice ups
3

Typical.

I re-tried SSH to a different AP (after multiple previous attempts) and the details have worked.

I was then able to edit the DNS servers in /etc/resolv.conf

1 Spice up
4

Glad to see you resolved your issue.

For future reference, the SSH credentials of the devices are managed by the UniFi controller. In the controller (you might have to enable Advanced Features in the site) you can find the credentials. If the device is in factory default configuration, the credentials are user ubnt and password ubnt.

If the device is visible on the network (i.e., can ping, can make an SSH connection to it), you can log in via SSH using the credentials found in the controller and issue a ‘set-inform’ command to reassociate the device with the controller. Type ‘help’ at the command line to see usage.

If the device is not visible, you may be able to temporarily connect it via wired network to reassociate it. While all of the UniFi product line claims to support meshing, I’ve found that some mesh topologies are unreliable. For example, I recently had an installation with two AC Meshes that wouldn’t reliably connect to AC Pros which were hardwired – and the distance between was not excessive (<100 ft). On the other hand, I’ve deployed an install with five AC Mesh Pros (where only one was hardwired) that has worked well. (In the unreliable situation, we ended up hardwiring the AC Mesh units.)

1 Spice up