ElderUsr's Blog

This document outlines a bunch of items/forum posts that I have used in the past for assisting in getting additional functionality/usage out of my Unifi Switches. The obvious is the Edge Switch CLI Command Reference Or for those that like it all shown out EdgeSwitch CLI Tree And a simple walk through straight from UBNT. Unifi Switch can be SCP'd into if needed. Credentials are typically under Settings -> Site ->  Device Authentication. Note: If you make any changes via the CLI using the Edge Switch subsection, it will be removed next time the switch gets provisioned from the Controller. (Reboot, or a physical change in the Controller).  You can keep the changes using json files within the USG, but Unifi has not stated that they will add support to allow this within the Unifi Switches. If you are planning on doing any huge configuration via the CLI, your better buying an Edge Switch instead. Commands: US.v3.7.55# telnet localhost //This allows access into ...

This document will outline how to configure from Factory Reset a Unifi 48-Port PoE Switch into a AWS Cloud Controller. 1. Reset your Unifi 48-Port PoE Switch by pressing and holding in the Reset button on the right-side of the switch for 5 seconds. 2. Verify that it is connected to the LAN that either your controller is located, or in this case a network that can provide DHCP Services and reach the internet for AWS Controller Registration. 3. Your Device will boot up with an acquired DHCP IP address. You can either find out the IP of the switch using the details provided from your local DHCP Server, or use a tool such as Zenmap or Nmap. 4. Once found, SSH into the device using ubnt/ubnt as the default login and password and perform set-inform http:// :8080/inform this will then allow your device to show up within the Unifi Controller for adoption. Note : You can also cat the /var/log/ on the server to get additional details if it is functioning or failing. 5. Make sure t...

After your controller has been built, you should configure it for Cloud Access. This will allow remote administration from your Android/iPhone for viewing/management of your devices/controller. 1. Create a Unifi Cloud Account at https://account.ubnt.com 2. Sign into your Controller and go to the Settings -> Cloud Access 3. Enable the Cloud Access, and populate it with your credentials created from the Unifi Cloud Account. 4. You should now be able to download the application on your mobile device for remote management.

This document assumes that you have already created an AWS Cloud Controller for Unifi + opened associated ports that are required for communication between the server and the endpoint. 1. Plug it all in, using the LAN port plug your PC in, and WAN port for your ISP. 2 Go to https://192.168.1.1 on your PC. 3. In the Inform URL section, type in your AWS Cloud Instance's URL and :8080/inform at the end of it such as: https:// :8080/inform 4. If that does not work, SSH into the device using ubnt/ubnt as the default credentials and perform the following commands: set inform https:// :8080/inform set inform http:// :8080/inform 5. Recheck your AWS Controller, it should now have an option for adoption such as below. 6. Log back into the USG via SSH, and issue the adopt/inform command again, it'll show another message about adoption within the Controller. You may need to do this twice. 7. It eventually will show Provisioning and then after a reboot with the new conf...

Building Site-to-Site B2B from Unifi USG to Fortigate (500D or other models) Fortigate Configuration 1. Build a New VPN Tunnel using Custom VPN Tunnel (No Template) 2. Under Network, point to the Public Side IP of the USG (Public IP, not WAN interface) 3. Leave everything else default (NAT-T Enabled, DPD Disabled..ect) 4. Authentication, use PSK and IKEv1 with Main 5. Phase 1 Purposal, set algorithms to AES128 and SHA1, with DH 14. 6. Phase 2 Purposal, set Local Address and Remote address to 0.0.0.0/0.0.0.0 and 0.0.0.0/0.0.0.0 respectively. 7. Set Encryption to AES128/Sha1, Replay Detection and PFS enabled, along with DH14. Enable Autokey Keep Alive, and Auto-Negotiate, and save changes. 8. Build a Static Route pointing to the Far-End Destination/Segment you want to reach. 9. Build a Policy Stating which Segments can hit the Far-End Destination/B2B USG Configuration 1. This is assuming that USG is already registered to the Unifi Controller. 2. Go t...