What you'll need
- Admin access to your Unleashed master AP or ZoneDirector controller
- Your MyWiFi RADIUS server IP and shared secret (from your MyWiFi location settings), if you're using RADIUS-backed login — RADIUS is the standard protocol WiFi hardware uses to ask MyWiFi whether a guest may go online
- Firewall access to open the controller's Northbound Interface port to MyWiFi's servers
- Note: this covers on-premises Unleashed and ZoneDirector only. If your APs are managed through RUCKUS One cloud, use the RUCKUS SmartZone article instead — Unleashed and ZoneDirector have no cloud provisioning option.
Steps
- In the controller, go to Admin & Services > Services > Hotspot Services (Unleashed) or Services & Profiles > Hotspot Services (ZoneDirector) and create a new Hotspot profile — RUCKUS's name for a captive portal, the mini-browser window a phone opens automatically when a guest joins a WiFi network.
- Set the Login Page URL to your MyWiFi splash page (the branded login page guests see when they connect) URL for this location, and set the Redirect URL to wherever guests should land after logging in.
- Under Authentication, choose one: to use RADIUS-backed login, add an AAA server pointing to MyWiFi's RADIUS endpoint with the shared secret and ports 1812/1813. Otherwise leave it on Local DB and MyWiFi will authorize guests directly.
- Enable the Northbound Interface under System > General Settings > Northbound Interface and set a strong password there. This is separate from your admin login — you'll enter the same password in MyWiFi.
- Assign the Hotspot profile you created to your guest WLAN.
- Add MyWiFi's splash page domain to the Walled Garden list (the small list of domains a guest can reach before logging in) on the Hotspot profile.
- In the MyWiFi dashboard, go to Devices and click Add Device.
- Select the Location, name the device, and under Select Your Hardware choose RUCKUS Unleashed or RUCKUS ZoneDirector, matching your controller type.
- Enter your RUCKUS connection details as prompted — typically the controller's management IP or hostname and the Northbound Interface password from step 4 — and save.
Best practice: Unleashed has no dedicated controller hardware — the "master AP" role can shift between your access points over time. Where possible, use a stable hostname rather than a raw IP address for the controller when entering your connection details, so the integration doesn't break if the master role moves to a different AP.
Comments
Please sign in to leave a comment.