![]() ![]() The main methods are outlined below: Connect via SSH on Windowsġ. There are various methods for this depending on the device/OS you use. If you can SSH into the device, it’s possible to 元 adopt via CLI command. Read our Ubiquiti UniFi Controller guide here to find out more about these methods. This is useful if you manage multiple offices centrally on a virtual machine or provide management services to end users. This is the most typical adoption method and is perfectly serviceable in most use cases.īut what if you are not on the same network? If your UniFi network controller is at a remote location, such as a head office, second premises or even hosted on AWS you can uses Layer 3 Adoption via SSH. L2 adoption on UniFi (where the devices and UniFi Network application are on the same network) uses self discovery, any locally-available, unmanaged UniFi Devices will appear as “Pending Adoption” in the UniFi Network application itself (in the Devices section). Once, re-connected via SSH, issue the same commands againĬongratulations! You can close the SSH window and your AP is ready to use on your network.Regular UniFi adoption is preformed over Layer 2. From there, you can also change auto-generated password to something easier to memorise. Go to the "Settings" panel > "Site" > "Device Password" on your UniFi controller. If you don’t know this, the device login username and password can be found in the controller software. Once it’s connected, you will need to re-SSH to the AP, in which it will now have the username/password credentials that are set by your controller. Then if you go to your controllers homepage and go to Access Points and you should see your access point in the list (you can verify this with checking IP Address you where connecting too).Ĭlick Adopt next to the AP, and refresh the page until the AP comes back with a status of ‘Connected’ (It may need to upgrade the firmware on the AP) Once logged in, enter the following commands, and remember to replace 192.168.10.2 with the address of your controller ![]() If you’ve got a new out of the box unit, the default credentials are: Once you’ve got the IP Address on your unit, use an SSH program such as putty to establish a connection to the AP. To find which IP address your UniFi is, on the back on your physical UniFi product, there is a “MAC ID”, compare the last 12 numbers to the Unique ID listed in the DHCP Table. Login to your Windows Server, in your start menu, go to Administrative Tools > DHCP Expand your DHCP domain and go to the scope for which you’ve got your UniFi’s plugged into. To find which IP address your UniFi is, on the back on your physical UniFi product, there is a “MAC ID”, compare the last 12 numbers to the MAC address’s listed in the DHCP Table. Go to IP > DHCP-Server > Leases and you’ll be able to see all the devices that have an IP Address. You’ll need to find out from your DHCP table what address your AP has. In this method you need to SSH on to each access point and statically point the AP at the controller. As per the network diagram, we’ll be putting in 192.168.10.2 Select your DNS Zone for which your device will be sitting in & right click on it and select New Host ( A or AAAA).įor the name, enter in “ unifi” without the quotes, and for the IP address, put the address of your UniFi server. Login to your Windows Server, in your start menu, go to Administrative Tools > DNSĮxpand your DNS server name and go to Forward Lookup Zones. Login to your Mikrotik router, and via CLI enter the following line: /ip dns static add name= unifi address=192.168.10.2 This will be the quickest method is you have lots of AP’s to setup. If your network looks after its own DNS server, or you have the ability to set a custom DNS record on your network, then this method is for you. Thus the same in return for the controller software looking for the access points. Because our controller is sitting on a different subnet, broadcasts get stopped at the router and are unable to make it to the controller software. ![]() UniFi access points sends out broadcast messages to look for their controller, these operate at a layer 2 level ( OSI Model) and are only sent within the broadcast domain. If your organisation has a lot of users/traffic, it is recommended to segment these into different networks to decrease broadcast domains and increase network efficiency. This guide assumes that you have already set up your UniFi Controller. Your wireless network at your site is on a different subnet to what your UniFi controller is going to be sitting on. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |