UniFi Cloud Key
-
@brianlittlejohn said:
@Dashrender I tried to add them via ssh and the set-inform address using an IP address and it would show up in the controller, but when I would go to adopt them it would start and say disconnected and never recognize it again.
hmm.. weird. Was your offsite router providing the DNS servers of your main network? Do you have a Unifi record pointing to your controller? Doing this has solved all of my problems.
By default the UAPs boot and look for unifi.localdomain.xyz. Assuming it resolves, that should be all that's required to connect them to your controller at your main office.
-
@Dashrender I didnt have DNS stuff setup, I didn't mess with it a whole lot, running short on time.
-
Just ordered mine.
-
Should be here on Wednesday
-
@brianlittlejohn Try it - it works REALLY well. Making a unifi record takes like 20 seconds in DNS.
-
@Dashrender Next time I am at that office I will. I don't go out there very often.
-
@brianlittlejohn said:
@Dashrender Next time I am at that office I will. I don't go out there very often.
Why would you have to wait to go out there? Or is there no gear there yet? I got lost on that part.
-
@JaredBusch I'm not going to make any remote changes I'm not sure of when I don't have the time to drive to the site (4 hour round trip)
-
@brianlittlejohn said:
@JaredBusch I'm not going to make any remote changes I'm not sure of when I don't have the time to drive to the site (4 hour round trip)
I was thinking the same as Jared, but I suppose your reasoning makes sense.
Though.. that said, do your UAPs check-in with your controller now? or were they setup with a controller on your laptop that isn't there any more? If they don't check in, or at least weren't setup by the controller at your main office, then adding unifi to your DNS won't matter.
Also don't forget, the DHCP server that's handing out IPs at the remote location needs to handout DNS entries for YOUR DNS servers, not the ISPs.
-
@brianlittlejohn said:
@JaredBusch I'm not going to make any remote changes I'm not sure of when I don't have the time to drive to the site (4 hour round trip)
It is a DNS entry.
If you do it right, then the AP shows up in your controller after the AP next reboots, or decides to recheck DNS after heartbeat failure.If you do it wrong, nothing visibly happens because the AP will still not point at your controller.
-
@JaredBusch said:
@brianlittlejohn said:
@JaredBusch I'm not going to make any remote changes I'm not sure of when I don't have the time to drive to the site (4 hour round trip)
It is a DNS entry.
If you do it right, then the AP shows up in your controller after the AP next reboots, or decides to recheck DNS after heartbeat failure.That part is easy... the issue will be changing controllers from what I used (which was on my laptop), to set it up to the controller at the main office. I don't imagine it going well and want to have the time available for me to go out there when it doesn't.
-
@brianlittlejohn said:
@JaredBusch said:
@brianlittlejohn said:
@JaredBusch I'm not going to make any remote changes I'm not sure of when I don't have the time to drive to the site (4 hour round trip)
It is a DNS entry.
If you do it right, then the AP shows up in your controller after the AP next reboots, or decides to recheck DNS after heartbeat failure.That part is easy... the issue will be changing controllers from what I used (which was on my laptop), to set it up to the controller at the main office. I don't imagine it going well and want to have the time available for me to go out there when it doesn't.
I've migrated entire clients sites from various on site controllers to my single off site controller.
There is seriously nothing to it. You make the new site in the controller, add the wireless network, then wait for the AP to show up on the default network needing adopted. Once there, you adopt it and move it to the appropriate site.
The UAP will not change their programming just because they see a new controller. That happens when you adopt them into the controller.
-
@brianlittlejohn said:
That part is easy... the issue will be changing controllers from what I used (which was on my laptop), to set it up to the controller at the main office. I don't imagine it going well and want to have the time available for me to go out there when it doesn't.
You're right. You'll have to rest the UAPs and attach them to the controller in the main office. You'll probably need to be onsite to reset the UAPs since you don't have an active controller controlling them now.
-
@Dashrender said:
@brianlittlejohn said:
That part is easy... the issue will be changing controllers from what I used (which was on my laptop), to set it up to the controller at the main office. I don't imagine it going well and want to have the time available for me to go out there when it doesn't.
You're right. You'll have to rest the UAPs and attach them to the controller in the main office. You'll probably need to be onsite to reset the UAPs since you don't have an active controller controlling them now.
You do not have to reset the UAP unless something is wrong with them. Even if there is, the bonus is that because it needs reset, the DNS changes will not affect it.
-
@JaredBusch said:
@brianlittlejohn said:
@JaredBusch said:
@brianlittlejohn said:
@JaredBusch I'm not going to make any remote changes I'm not sure of when I don't have the time to drive to the site (4 hour round trip)
It is a DNS entry.
If you do it right, then the AP shows up in your controller after the AP next reboots, or decides to recheck DNS after heartbeat failure.That part is easy... the issue will be changing controllers from what I used (which was on my laptop), to set it up to the controller at the main office. I don't imagine it going well and want to have the time available for me to go out there when it doesn't.
I've migrated entire clients sites from various on site controllers to my single off site controller.
There is seriously nothing to it. You make the new site in the controller, add the wireless network, then wait for the AP to show up on the default network needing adopted. Once there, you adopt it and move it to the appropriate site.
The UAP will not change their programming just because they see a new controller. That happens when you adopt them into the controller.
Jared, will the new controller even list the AP since the AP is configured for a different controller? That would seem very bad if you could just steal APs at will like that. i.e. I don't like your company, I find some way to bring my rouge controller up on your network, see all of your APs (OK I've poisoned the DNS too, yeah I'm reaching, but go with me) now I can just just steal your APs onto my controller.
I was pretty sure I read you had to reset the AP to change them to a new controller. Of course the reset can be performed by the trusted controller, then when it resets, all controllers would see the AP as a non associated AP or you can press the rest button on the device.
-
@Dashrender @JaredBusch Im worried that with the previous experience I had with them starting the adoption then not communicating again that it may happen again... Anyways this is not a big deal, one AP in a small office. I dont have a very big UNIFI infrastructure anyways... im running Cisco APs at the main office (as they fail I will replace them with a different brand) I'll just have it on my agenda next time I decide/have to go out to that site to play with it some more.
-
This is almost a poor man's Meraki.
-
@Dashrender said:
This is almost a poor man's Meraki.
Except it works better and is more powerful. It's more the smart man's Meraki
-
@scottalanmiller said:
@Dashrender said:
This is almost a poor man's Meraki.
Except it works better and is more powerful.
You're going to need to explain that one to me. There don't seem to be near the options in Unifi that Meraki has.
-
@Dashrender What useful features do you see missing? And you have to compare things like "features" to things like performance, cost and reliability. It takes a LOT of "features" to overcome performance, for example.
