Username is ubnt and IP address 192.168.1.20, so enter "ssh -l ubntģ) Type Yes to accept the certificate, and press Enter key.Ĥ) Enter your device's password, by default it's "ubnt".Īfter that, please try setting the inform URL by following these
UNIFI MAP DESIGNER TOO WHITE MAC OS
Into your device using PuTTY for Windows or Console on MAC OS X.Ģ) Enter Hostname IP address (by default is 192.168.1.20), leave port asĭefault and make sure you've selected protocol SSHĤ) Accept the certificate, then enter your username and password (by defaultĬredentials are ubnt in both cases) and press Enter keyĥ) If it works properly you will see XM5.x and a $ symbol, there you can enterġ) Open Terminal (Console) under Program and UtilitiesĢ) Enter command "ssh -l (USERNAME) (IP ADDRESS)", by default If yes, we need to use putty to SSH into the device. Please check if you're able to ping the UAP? You can check the IP address from dhcp or you canĭownload advanced IP scanner from the link given below:Īlso, considering that the UAP is in the same subnet, could you If the UAP doesn't show up, we need to check if the device is
The controller machine and check if the UAP is discovered in the discovery tool I'd suggest you disable firewall and any antivirus running on Then i disconnected the UAP and reconnected it to my regular network, ssh'd into it again and again gave the set-inform command, only now with the IP from my real UNIFI controller, adopted it, and finally it is working now as it should. Next i changed the IP of the UAP from DHCP to STATIC and gave it a IP from my normal network. Then i started UNIFI and ssh'd into the UAP and did a "set-inform http:/ Opens a new window / 192.168.1.101:8080/ inform"Īfter a minute or so i could adopt the UAP. When i booted everything up i could see the the UAP got IP 192.168.1.100 and my laptop 192.168.1.101. The solution for me was, creating a new network with a Linksys 120n router in factory default state, a laptop with UNIFI installed and the UAP. Resetting the UAP did not make a difference, it still wasn't assigned a IP address. When i first hooked my UAP's on my network they got a IP from the ASA 5505, but when that lease expired for some reason the ASA didn't give the UAP a new lease, therefore the UAP became without a IP and became in a disconnected state but was still serving clients. Well, i finally got both the UAP AC's up and running again and it looks like the problem is a combination of a Cisco ASA 5505 (my router/firewall/dhcp server) and the UAP AC's.
0 kommentar(er)
