![]() Its much easier to just plug in the factory default device, use Ubnt Discovery tool to set the inform to your remote hosted controller, and be done with it." Our firewall has multicast support disabled. 1st the right subnet, and then the 192.168 default IP subnet that factory default goes to. Seeing the tail log too, I saw it kept trying to contact the laptop's IP's. I can use the laptop as the controller again, but that's just doing what I was doing before. And of course, the controller doesn't see it.Default ssh pwd doesn't work: ubnt, and my former ssh pwd doesn't work- how am I supposed to set the inform-url?.Syswrapper.sh restore-default, it gets an IP on the right subnet (that's great right, supposedly), I think I've exhausted all possibilities here- I'm really not sure what to try next! Regardless, the other AP's have their inform url set to its IP- no big deal, I already tried that. I even have the AP set as the exact same IP as it used to be, and with the laptop as its controller, I was able to set the right dns settings as well, so it should see the controller's A record. Yet after hours of testing this, the controller still doesn't show the AP! Wireshark on the controller picks up TCP/HTTP traffic to the trouble AP- so they're communicating. But the controller's main IP is on another subnet- there's just a route to the other subnet.Ĭontroller is on 192, and wireless is on 10.0.Ĭontroller is able to ping all AP's.even the troublesome one. The thing is, when I use a laptop as the controller on the same subnet, it sees it. I also rebooted the controller last night. I tried every form of url I could think of, but set-inform does not work. I tried the DNS name, the IP, https/http, 8080, 8443. I did a set-inform for the troublesome AP. Remove any restrictive firewall rules that would prevent IP connectivity between the device and console.I was able to get the actual inform url by SSHing into another AP that is recognized by the controller.If adoption fails, that means the selected WiFi lacks connectivity with the console running UniFi Protect. Select a WiFi that has connectivity to the console running UniFi Protect, and enter the password.If it does not appear, ensure Bluetooth permissions are enabled on your mobile device.Move closer to the device and click the pop-up once it appears.Download the UniFi Protect Mobile App ( iOS / Android) and sign in.Devices can only be moved to a different network/VLAN after they are adopted.Įnsure the UniFi device is powered on, as indicated by an illuminated LED light.Check the IP address of your device to confirm if it is on the same network as your UniFi Console. If you are not sure how to do this, click here.Verify that all switch ports between the new device and your network's gateway and DHCP server have been properly tagged to allow network traffic.If you are using a UniFi Gateway or UniFi Cloud Gateway, these ports are already open by default. ![]() Open TCP Port 7444, 7550, 7442, and UDP Port 10001 locally (LAN) on all gateways and firewalls.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |