Set up Peplink InControl 2 with MyWiFi

What you'll need

• Admin access to your Peplink device (via the local device admin UI, or InControl 2's per-device settings)
• A MyWiFi location already set up, so you have a splash page URL to paste in
• A valid SSL certificate installed on the AP/controller — a self-signed certificate will cause browser warnings that break the login flow
• If you plan to authenticate guests over RADIUS, know that this is configured per-device, not through InControl 2's built-in hosted captive portal (see the note below)

Steps

1. On your Peplink device (in the local device admin UI, or via InControl 2's per-device settings), go to Network > Captive Portal.
2. Set the authentication mode to External Splash Page.
3. Paste your MyWiFi splash page URL for this location into the splash page URL field.
4. If you want RADIUS-backed authentication instead of (or alongside) the external splash page, go to Network > RADIUS Server on the device and enter MyWiFi's RADIUS server IP, auth port, shared secret, and accounting server details.
5. Add your MyWiFi portal domain (and any related asset domains) to the Allowed Networks / walled garden list in the captive portal config, so guests can reach the login page before they're authenticated.
6. In the MyWiFi dashboard, go to Devices and click Add Device.
7. Select the Location, name the device, and under Select Your Hardware choose Peplink.
8. Enter your Peplink connection details as prompted and save.

Best practice: Peplink's InControl 2-hosted captive portal and its RADIUS integration are mutually exclusive at the cloud level — InControl 2's built-in portal does not support RADIUS at all. If you need RADIUS authentication, you must configure it at the individual device level rather than through InControl 2's managed portal UI.

Related articles

• Datto Networking / OpenMesh (CloudTrax)
• Generic RADIUS / WISPr