Thought I'd check, though, since otherwise I'll have to SSH to each device and point it manually.Īnother option is to map the hostname "unifi" through DNS, but I don't believe I can do that with the FortiGate either, as it requires a domain to be specified and the UniFi gear needs it without a domain.
#DHCP UNIFI CONTROLLER CODE#
option space ubnt option ubnt.unifi-address code 1 = ip-address class "ubnt" įrom what I've been able to see of the DHCP Option the FortiGate exposes, I probably can't do this without a separate DNS server.
Per the UniFi docs, I could do this by having DHCP Option 43 look like the following Linux example pulled from their docs: I'm trying to make setting up some Ubiquity (UniFi) devices behind a FortiGate somewhat simpler, by providing info in DHCP Option 43 to point the UniFi devices to the UniFi controller (which is not on the same subnet).
Per the UniFi docs, I could do this by having DHCP Option 43 look like the following Linux example pulled from their docs. To add the option to an existing DHCP scope, navigate to the DHCP server. I'm trying to make setting up some Ubiquity (UniFi) devices behind a FortiGate somewhat simpler, by providing info in DHCP Option 43 to point the UniFi devices to the UniFi controller (which is not on the same subnet). This setting will ease the discovery and adoption of UniFi devices and is useful when the application is located on a different subnet. Anybody successfully set up Additional DHCP Option 43 (config sys dhcp server > config options) to map a url to IP for a third party vendor? The UniFi Network application option will allow UniFi devices to automatically discover the location of the UniFi Network application.
0 kommentar(er)
