What I Use: UniFi/Ubiquiti Access Points
Posted on June 22, 2016 by Richard Brynteson in What I Use
Every once in a while I get asked what do I use at home/small office and today I figured what a great opportunity to blog about home WiFi. So this is a new post in my What I Use series. Before continuing, it should be noted that I purchased all of the equipment I’m about to talk about and Ubiquiti Networks didn’t give me a deal, didn’t ask me to blog or anything else. i.e. all content are my own thoughts.
What I Used Before
Like so many in the home office I was simply using what was provided to me by my internet provider – in this case Comcast. So I had started with the Comcast Modem, was paying my $9.95 per month and using their wireless access point built into the device. Needless to say, it wasn’t a great experience. Coverage was spotty, I was paying for a modem and randomly throughout the day the modem would drop down to 250k and only a reboot would fix it.
So about three months ago, I purchased my own cable modem and used an old NetGear wireless access point. This solved the random speed drops to 250k but wireless was still spotty and got significantly worse when the kids (and their friends) would come over. At times we had 25+ devices on the WiFi.
The solution is two AP-AC-Pro access points and the Unifi Security Gateway. Additionally, to control all of this you need a server/workstation/something to act as a controller for your environment. In my case, I’m going to use my home windows server for this (NOTE: Since using the Windows box I’ve discovered there are a few things the controller won’t do for me – maybe Linux would have been better.)
Setup of Devices
The setup starts with the install of the controller. Needless to say, the install is a quick “next-next-next” type of installer. There aren’t any difficult questions to figure out or do. There are a couple of pre-reqs:
- Java 7 or later
- Port 8080 and 8443 must be open/available
When the installer is done, I would recommend moving the folder. By default, it gets installed to “%windir%\users%username%\Ubiquiti UniFi” which is a silly place to install anything. The good news is, simply move the folder to a new location. I would recommend “%windir%\Program Files\Ubiquiti UniFi” as a location.
Once you have install the product, you can launch the controller software. A shortcut would have been placed on your desktop (we will talk installing as a service later) – if you moved the install folder make sure to update your shortcut. Once the software is running, browse to https://localhost:8443 to start the process.
Setup and Config
When you visit the site for the first time it will display the devices it found on the network. In my case, two AP-AC-Pro access points. I added the gateway after I had the WiFi up and running.
Enter the SSID, Password and choose if Guest Access will be enabled.
Next, enter your username and password for the controller. It’s good to note that this combo will also be the SSH/Console credentials needed for each individual device.
Click Next and it shows a summary of settings and you are done. The controller will now configure the access points to how you want them.
Once your controller is setup you will see the following dashboard. This allows you to see the currently connected device, daily and hourly throughput and latency on the network. Additionally, you can configure advanced items such as periodic speed tests and more.
Adding New Equipment
As you add new equipment to your UniFi network it will appear under the devices tab.
As those devices are discovered, you simply click the “Adopt” button on the far right side and the controller will take control of the device. It should be noted that any already configured devices do not appear in this list so a factory reset might would be required if you setup these devices previously.
Zero Handoff or RSSI
One feature that many high-end controllers have is zero handoff. This allows a computer to seamlessly connect to another WiFi access point as you travel around your building. This feature relies on the idea that all access points in your deployment use the same channel for wireless. This might work really well in an office building or corporate location where density is low but at home, having to force all devices to a specific channel, may not be ideal. As I write this post, I see 9 different WiFi access points being advertised. I want my controller to move the channels around whenever it wants because my neighbors seem to add new SSID’s on a daily basis for some reason. Lastly, for me, I don’t randomly walk around with my laptop throughout the house. And I NEVER use the Skype for Business Mobile client (mainly because the Windows Phone version is terrible). So the zero handoff is really not needed for me.
But I have another concern. My basement (where one of the access points was placed) had terrible performance in the past.
So in the end, I decided to use a Minimum RSSI setting. What this will do is kick the device off of the access point and force a reconnect if I travel too far away (i.e. signal gets too low). The idea is that my access point in the basement will only serve the devices in the basement and as I move to the higher levels in the house the signal would be too weak, kick me off, and then use the upstairs access point instead.
I currently have my Minimum RSSI set to a -75 dBm in the Controller.
NOTE: This setting used to be done via a config file only and the math/name was different previously. So before you may have set a minrssi of 20 – per this guide. Based on what I’ve found, the naming is a little goofy so a -75 is actually a value of 20 that is listed in the guide. Essentially, take -95 + -75 (your value) to get what the old config file would have done.
Thus far in my testing, this has worked exactly as I expected devices have connected where I wanted them to connect. As I walk up the stairs from my basement, my device disconnected and reconnected to the other access point. In all, it takes about 1 to 2 seconds to handoff between devices. And again, I don’t walk around with my laptop open so I’m in good shape.
Run As A Service
As I mentioned before, if you installed the controller software on a windows server/workstation it is not setup to run as a service by default.
Ubiquiti has a document here on how to configure the controller software as a service. The installer should really do this for you but the configuration is pretty easy.
So I’ve been using my Ubiquiti equipment now for the last two weeks and I have to say the performance is outstanding. I no longer get complaints from the family that the wifi is down, the internet is slow, etc. And my SfB calls no longer go red in every single call like before.
My next purchase (if I can ever find a store with them available) will be two 8 port Ubiquiti switches. These devices support PoE, QoS, etc. And they aren’t very expensive based on what I’ve seen online.
The only item that doesn’t work on my network anymore is my SpectraLink 8440 test device. I’ve done the research and it appears as though the AC-AP-Pro do not have WME enabled by default. This isn’t set in the Controller GUI so I’ll need to push a config file to the devices to enable this. Maybe a future post but I never used the device except for a few test calls.