Implementing Stampede within UniFi is a quick and simple process but there are some items we require to get this implemented successfully.
We do not integrate directly with UniFi.ui controllers.
UniFi.ui provides an ideal method for managing your controllers remotely in one place. While this is perfect for configuration and remote setup, UniFi.ui does not play well with captive portals. It creates a block between our API and the controller itself and prevents authentication requests from reaching the controller, resulting in captive portal login errors.
Implementing Stampede
Set up the controller to be reachable externally by configuring port forwarding from the router's Public IP to the controller via ports (80/443/8443). We require access to the GUI from our office to allow us to view the configuration and require our API source and destination IPs to gain access to the controller as well.
Contact support@stampede.ai for the IP addresses linked to our services.
We require a local admin account on the controller (this doesn't require an email address) and for those credentials to be passed to the team.
Ensuring Success
-
The controller is available remotely via its Public IP to our office (for the GUI) and the API source and IP addresses on ports (80/443/8443).
-
Desirable: The controller has a hostname and a valid SSL certificate
-
Have a local user admin account on the controller
With this setup, we can configure the Stampede integration and all the captive portal settings will be applied automatically to the hotspot settings. From there all that is required is for the captive portal to be enabled on the guest WiFi.