Sign in

Unifi Controller For Mac

Download here

  1. Download Unifi Controller For Windows
  2. Unifi Controller For Mac Download
  3. Unifi Controller Download For Mac
  4. Unifi V4.7.5 Controller For Mac

As an additional exercise in securing my home network, I decided to delve into how IEEE802.1x or dot1x works.

I have a unifi-based setup (USG, USW and UAP) and a lot of my setup is wired. I found setting this up for a wireless network is near to trivial (take care to choose the correct mac-address format and stick to it), I found configuring it for a Windows client somewhat less trivial. Read on if you want to know how I fared.

Wired autoconfig or not wired autoconfig?

  • Unknown MAC Address Listed Under Devices in UniFi Controller Title says it all, I have an unknown MAC Address listed in my UniFi Controller and no amount of Googling can help me identify the device. Any ideas on how to trace it or otherwise determine what it is.
  • The UniFi ® Controller software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance. A single UniFi Controller running in the cloud can manage multiple sites: multiple, distributed deployments and multi-tenancy for managed service providers.

Because dot1x is a port-based authentication protocol, I figured my Windows client should be ready to perform this authentication protocol. A lot of posts talk about the “authentication” tab on the network adaptor properties, but I did not see such a thing.

Turns out, you will have to enable the Wired Autoconfig service, as described here. Starting this service will enable the authentication tab, but then what? In my case, the connection kept turning up as ‘Authentication failed’.

Unifi set-up

So I diligently set up users on unifi, consisting of mac-address users using the mac address as both username as well as password.

Then, I had my wired auto-config Windows (10)-client happily zooming away on a port that I had assigned access to a certain network based on a proper 802.1x authentication. However, the client kept reporting authentication failed-errors and subsequently was connected to the fallback network (in my case, a “guest”-network with only access to the internet).

I believe I tried all authentication options on the windows client (MS-AKA, MS-CHAP), all to no avail…

Finding the culprit

Final config

As of the current controller version (check), it turns out this option is enabled by selecting “mac-based” on the port authentication type. Wrongly so, as the earlier linked post points out. As mac-based and MAB are apparently two completely different things.

Therefore, I did not need to enable the wired autoconfig service, but would simply enable “mac-based” on the port profile, and make a RADIUS-user entry for the all capitalized mac address of the client!

A word of warning

Stay tuned for this!

Taken from: http://jzdocs.com/manually-adding-ubiquiti-unifi-access-point-to-unifi-contoller/

This is the process to add a new Unifi AP to the Unifi controller when discovery doesn’t work. In our case, we have a central Unifi controller managing APs on multiple networks. But, the routers don’t allow the discovery tool to see new APs on other networks, so this is how we add one. In this example, we’ll say the Unifi controller is at 192.168.1.55.

1) Write down (or take a picture on your phone) the MAC address for the new AP.

2) Connect the new Unifi AP.

3) Check DHCP to see what IP address was given to the Unifi AP by searching for the MAC address in the DHCP clients table.

Once you have the IP, we’ll use putty to ssh into the device. In this example, we’ll use 192.168.1.185.

NOTE: If the AP has been provisioned before, you’ll have to use the password for the Unifi controller it was provisioned by.

login as: ubnt

Download Unifi Controller For Windows

Unifi Controller For Mac
Unifi Controller For Mac

>

NOTE: If the AP has been provisioned before, you’ll have to reset it to factory defaults. to do that, use the following command, and then SSH back into the device when it comes back up.

> syswrapper.sh restore-default

Since this is a brand new AP for us, we just need to do this:

> set-inform http://192.168.1.55:8080/inform

Next, we go connect to the Unifi command center. In a few minutes, we should see an alert stating a new device has checked in. If you don’t see the alert, check the device list, it should show up there as “Unknown”. From either location (alerts or ap device list), you should have a button that says “Adopt”. Adopt the new AP and go back to the SSH shell.

Send the command again, this should allow the AP to see that it has been adopted.

Unifi controller download for mac
Unifi controller download for mac

> set-inform http://192.168.1.55:8080/inform

Now you should see the new AP provisioned in the Unifi controller and you can edit the name and update the AP firmware.

Same steps as above with initial Unifi Controller settings:

Here are the instructions for setting up the UAPs on the new Unifi Controller software. Make sure you configure the following sections on the server:

Under settings (lower left cog)

  • Wireless Networks, configure the SSID(s) and security you are currently using with them.
  • Networks, Edit LAN and set the correct Subnet.
  • Admins, create any additional accounts you may want/need.
  • Controller, Enable the SMTP Server, configure it, and test to make sure it works.

Unifi Controller For Mac Download

Unifi Controller Download For Mac

  • You should set the UAP back to factory defaults to make sure it connects to the new controller properly. Make note of the UAPs MAC address to reference in the DHCP server once the UAP comes back up in factory default mode. To reset to factory, issue the following command:
  1. > syswrapper.sh restore-default

Keep in mind that this will revert it back to using DHCP on startup, etc. So check your DHCP server using the MAC address referenced earlier to see the new IP address

Unifi V4.7.5 Controller For Mac

  1. > set-inform http://server-ip-address:8080/inform
  • Check the Unifi Controller, it should have a message that a UAP is available to adopt, adopt the UAP
  • Back on the UAP send the command again:
  1. > set-inform http://server-ip-address:8080/inform
  • Finally, back in the Unifi Controller, you can set the name, upgrade the firmware, etc.

Download here