From PowerShell or CMD:
cd C:\Program Files (x86)\fournova\Tower\CompareTools
code .
Edit VisualStudioCode.json and replace line 10 which is:
This document provides some basic guidance on how to customize the Unifi Controller v5.6+ Hot Spot Portal feature. Existing documentation seems to be scarce in this technician's opinion.
This readme is the culmination of some exploration in customizing the portal for business use. Please note, all examples use the installed location of the Unifi v5 Controller software on the Unifi CloudKey.
Some issues have been encountered after upgrading the Unifi Controller to newer releases specifically with the Hot Spot Portal customizations on Unifi Controller versions greater than 5.10 relating to the use of these instructions. You may not have a choice but to upgrade your included default template to the latest version and re-modify your portal files.
When using a USG with Ubiquiti's Unifi Controller software (version 5.6 and earlier), the functionality of integrating the hostnames of clients (when they request a DHCP lease) into local DNS does not appear to work as you would find with Consumer grade routers. To work around this limitation, we can add static host mappings to a configuration file that will be provisioned to the USG when either a configuration change is made or we force provisioning to the USG itself.
I've added in the necessary syntax for adding Cloudflare DDNS to the USG for VPN/Services setup courtesy of this post by britannic on the Ubiquiti Forums.
# This file contains only partial paths to match on | |
# This file should reside in the same directory as the haproxy.cfg simply due to the way it is configured in the sample snippet-but they can go anywhere in the /etc/haproxy directory | |
/my-partial- https://subdomain3.mydomain.com/my-new-full-path |
Why, that's simple! Copy this script to your USG, run chmod +x on it and then, as a user with sudo permission, execute it.
Shamelessly borrowed from Brittanic on the Ubiquiti Unifi forums
Simply run the following command (note, if you are at all security concious-don't run it and instead review the script, then copy it to your USG to execute).
curl https://gist.githubusercontent.com/troyfontaine/7e6f93e32621177fc9a94e823adc52b5/raw/fix_ddns.sh | sudo bash
TFTP is said to "only use UDP 69" but this is completely and totally inaccurate.
TFTP starts communications on UDP 69, then moves the conversation to ephemeral ports between the two systems-and depending on the systems involved, they can change during the boot process.
Note, this doesn't seem to work across VLANs....
So, where do you start?
Step 1) You need UDP 67, 69, 4011, 1024:5000 from your PXE booting machine to the PXE Server. This is because the PXE bootloader appears to use that range specifically.