Clear, cut and straight to the point. Great video. Also to add for anyone that may encounter your device going offline after adopting. Just repeat these steps and it will finally stay online. Just remember the default ubnt is replaced with your unifi controller credentials now since you already adopted it the first time.
Hello sir , I have installed 3 unifi wifi in 3 different location .I set the name of one office fleet and second office Kapoor and third office Khalid . The main issue is that when I go any office it's show 3 wifi in any office .it should one wifi show where I go .please resolve my issue .thanks
I have also found that you can do host override on "unifi.localdomain" to point on the unifi's IP and will work. Depending on your network you might need to change the ".localdomain" part.
Actually, by default all Unifi devices look for the controller at hostname 'unifi', however if the Unifi device has a DNS suffix configured (either manually or via DHCP), then it will by default look for a controller at hostname 'unifi.'. So, I've found the easiest way to configure/adopt Unifi devices over an L3 network is via DNS (method 2 in this video) but just create an A record for 'unifi' and you can cut out the step of SSHing to the unifi device to set the inform host. This will work if your DHCP servers are pushing out the IP addresses of your internal DNS servers (which they already most likely are).
Unifi had a chrome app that will find local devices and let you point them to the controller. I also like to join where the controller is local, and then deploy to it's final destination.
Great video. I'd already configured the UniFi Controller option on my ER4, but never knew what the correlation was to my UniFi environment and what it was actually for until now.
I'm having one hell of a time trying to do this for one of my remote offices. I have APs in Denver that I'm trying to point to a cloud key gen 2 in DC. and the set inform command goes through, but the controller never see's the ap trying to talk to it
Here my 2 cents. First I think it's funny you forgot the most obvious one. You made it unnecessarily complicated by using a "specialisated" DNS-Name. If you'd set "unifi" instead of "toasty-unifi" as a DNS Name there would be no need to manually use set-inform. Of course just using "unifi" as a hostname would also work (if you don't prevent it through your DNS Server). It mostly don't work on 2 different networks, because they don't share DNS. If you decide to not create "unifi" as DNS-Entry it's ALWAYS recommended to set DHCP 43. If you need to add a new device you can access it directly through the controller. You don't have to look for the IP and do it manually that way. It doesn't matter if you set a static ip. For the IP config you still point to your DNS Server and it'll notice if the IP of the controller changed.
Agreed, it is a good video in general and helpful but it's indeed missing that obvious one as you say. A small addendum included in the video should be made to point out that mapping unifi.yourdomain to either a DNS A record of the controller's IP address or via a CNAME to the FQDN (if hosted publicly) is by far the simplest method to adopt new devices. Option 43 is as effective but is considered a legacy method, especially since the majority of all routers & switches nowadays allow for the editing of their DNS table.
Does option 43 work with the cloud controller? I work at an MSP and our cloud controller is set up to have a site per client. Is there any way I could automate the process so that it would add the AP to the correct site controller on our cloud console?
Layer 3 of the OSI model means that you have all 3 layers available and no more, therefore making use of protocols that do not need tcp/udp (and ip) for the adoption process, as these are level 4 of OSI. Routing is irrelevant, as that is higher level protocols. If it was using IP, then assuming correct routing, you'd simply connect by IP....but then it wouldnt be called Layer 3.
5:38 for UDM Users under network version 7.2.94 the user informaiton can be found under: settings wheel->system->NETWORK DEVICE SSH AUTHENTICATION. it has to be enabled to work too!
If you feel inclined, you can donate at pay.toastyanswers.com I used to have a donation section on my website, but I've taken that down since it wasn't used very often.
@@ToastyAnswers No matter what amount I put in the Pay button at the bottom is greyed out and it won't let me submit. Do you know what I may be doing wrong?
Clear, cut and straight to the point. Great video. Also to add for anyone that may encounter your device going offline after adopting. Just repeat these steps and it will finally stay online. Just remember the default ubnt is replaced with your unifi controller credentials now since you already adopted it the first time.
Hello sir ,
I have installed 3 unifi wifi in 3 different location .I set the name of one office fleet and second office Kapoor and third office Khalid .
The main issue is that when I go any office it's show 3 wifi in any office .it should one wifi show where I go .please resolve my issue .thanks
How can we do this for the dream router? Using the SSH to inform, but the adoption never turns up in the console.
I have also found that you can do host override on "unifi.localdomain" to point on the unifi's IP and will work.
Depending on your network you might need to change the ".localdomain" part.
Actually, by default all Unifi devices look for the controller at hostname 'unifi', however if the Unifi device has a DNS suffix configured (either manually or via DHCP), then it will by default look for a controller at hostname 'unifi.'.
So, I've found the easiest way to configure/adopt Unifi devices over an L3 network is via DNS (method 2 in this video) but just create an A record for 'unifi' and you can cut out the step of SSHing to the unifi device to set the inform host. This will work if your DHCP servers are pushing out the IP addresses of your internal DNS servers (which they already most likely are).
Remember to turn off firewall of your antivirus if you still can't see it and that the controller's IP is the PC's ipv4 address
Unifi had a chrome app that will find local devices and let you point them to the controller. I also like to join where the controller is local, and then deploy to it's final destination.
Great video.
I'd already configured the UniFi Controller option on my ER4, but never knew what the correlation was to my UniFi environment and what it was actually for until now.
I'm having one hell of a time trying to do this for one of my remote offices. I have APs in Denver that I'm trying to point to a cloud key gen 2 in DC. and the set inform command goes through, but the controller never see's the ap trying to talk to it
Here my 2 cents.
First I think it's funny you forgot the most obvious one.
You made it unnecessarily complicated by using a "specialisated" DNS-Name.
If you'd set "unifi" instead of "toasty-unifi" as a DNS Name there would be no need to manually use set-inform. Of course just using "unifi" as a hostname would also work (if you don't prevent it through your DNS Server).
It mostly don't work on 2 different networks, because they don't share DNS.
If you decide to not create "unifi" as DNS-Entry it's ALWAYS recommended to set DHCP 43.
If you need to add a new device you can access it directly through the controller. You don't have to look for the IP and do it manually that way.
It doesn't matter if you set a static ip. For the IP config you still point to your DNS Server and it'll notice if the IP of the controller changed.
Agreed, it is a good video in general and helpful but it's indeed missing that obvious one as you say. A small addendum included in the video should be made to point out that mapping unifi.yourdomain to either a DNS A record of the controller's IP address or via a CNAME to the FQDN (if hosted publicly) is by far the simplest method to adopt new devices. Option 43 is as effective but is considered a legacy method, especially since the majority of all routers & switches nowadays allow for the editing of their DNS table.
Does option 43 work with the cloud controller? I work at an MSP and our cloud controller is set up to have a site per client. Is there any way I could automate the process so that it would add the AP to the correct site controller on our cloud console?
Layer 3 of the OSI model means that you have all 3 layers available and no more, therefore making use of protocols that do not need tcp/udp (and ip) for the adoption process, as these are level 4 of OSI. Routing is irrelevant, as that is higher level protocols. If it was using IP, then assuming correct routing, you'd simply connect by IP....but then it wouldnt be called Layer 3.
5:38 for UDM Users under network version 7.2.94 the user informaiton can be found under:
settings wheel->system->NETWORK DEVICE SSH AUTHENTICATION.
it has to be enabled to work too!
Good stuff thx
Great as always. I don't see a donate button on your channel. How can I donate for all the work you have done?
If you feel inclined, you can donate at pay.toastyanswers.com
I used to have a donation section on my website, but I've taken that down since it wasn't used very often.
@@ToastyAnswers No matter what amount I put in the Pay button at the bottom is greyed out and it won't let me submit. Do you know what I may be doing wrong?