12-03-2012 02:37 PM
Value: ubnt.unifi-address 10.29.0.157
This is the FAQ we're pulling the details from: wiki.ubnt.com/UniFi_FAQ#To_use_DHCP_Option_43
Do we need more options?
03-07-2013 03:53 PM
- have a DHCP reservation for the controller PC, with DHCP hostname set to unifi,
(with the DNS forwarder setting ticked to resolve for DHCP reservations)
- have a DNS forwarder entry for unifi (unifi.example.suffix) which works even if the controller is outside the network
In either case it doesn't matter whether the controller machine hostname is really unifi or not.
The first method is slightly neater as it both reserves the IP of the controller machine and resolves the name in one setting, so the controller's network settings can remain on automatic.
Also if you ever have to setup a replacement controller machine you can prep it, then shut down the existing controller machine, then update the MAC address (in the DHCP reservation) when ready to attach the new one to the network.
04-13-2013 01:36 AM - edited 04-13-2013 01:36 AM
I worked this out:
Use DHCP option 43 and select "String". You must convert your controller IP address to HEX and add 01:04 to the beginning ie. for my setup - IP = 10.0.0.10 in HEX it is 0A:00:00:0A so in the 'String' field I enter:
Hope this helps.
07-08-2014 08:30 AM - edited 07-08-2014 08:35 AM
Trying to make it simpler for ppl
Additional BOOTP/DHCP Options -> press advanced and add a new entry.
(01:04: + 192.168.110.10 in hex) 192.168.110.10 is unifi controller in this case.
Use http://www.kloth.net/services/iplocate.php to convert your controller ipadress.
Check dhcplease and ssh to AP with (ubnt/ubnt) before adoption and unifi user/pass after to check status.
Use help and info commands to get status.
Unable to resolve (http://unifi:8080/inform) <-- cannot resolve unifi hostname or option 43 not present in dhcpd answer.
Server Reject (http://unifi:8080/inform) <-- AP can reach server but is not adopted yet, login to controller and adopt.
Connected (http://unifi:8080/inform) <-- AP adopted in unifi controller. Yippie!
Hope this help
12-02-2014 04:09 PM
By the way, in case anybody is running a captive portal on pfSense (or any other router for that matter) while trying to configure Layer 3 adoption for their UniFi access points, don't forget to either whitelist the hostname for your controller or pass through the MAC's of your AP's.
I just spent a fair amount of time wondering why I couldn't get the darn things to inform to my controller over L3