Ruijie Integration

Guest WiFi on a Ruijie / Reyee EG gateway using its external portal (WISPr) + Captivo RADIUS. The gateway redirects guests to Captivo's hosted portal — no HTML upload.

1Register the gateway in Captivo

In Captivo: Settings → RADIUS → add the EG gateway's RADIUS source IP and the same shared secret as a NAS client.

2Enable the external (Web Auth) portal

On the EG gateway (Reyee/Ruijie Cloud or the local web UI): Authentication / Web Authentication → enable it for your guest SSID or network, and set the authentication type to External / Third-party portal. Open networks (no WPA) are typical for guest WiFi.

3Point the portal URL at Captivo

Set the External Portal / Auth Server URL to your Captivo-hosted portal address: https://app.captivo.io/p/<your-tenant-slug> — you can find this exact address in Settings → Portal. The gateway redirects unauthenticated guests there with its WISPr login parameters; the page submits the guest's credentials back to the gateway, which validates them against Captivo RADIUS.

There is nothing to download for Ruijie — the portal is served by Captivo. You only paste the URL above into the gateway's external-portal setting.

For the Active Sessions list to work: enable RADIUS accounting (port 1813) AND make the device send periodic accounting updates. Captivo treats a session as live while the device keeps signalling it; if only a start and a stop are sent, a guest who is still online drops off the list after 10 minutes while the device's own screen still shows them. The setting is usually called Interim, Accounting Interim Update or Update Interval; one minute is a good value.

4Add the Captivo RADIUS server

In the gateway's RADIUS / authentication-server settings add Captivo: Server = your Captivo RADIUS public IP/FQDN, Authentication port = 1812, Accounting port = 1813, Authentication method = PAP, and the shared secret you'll also register in Captivo. PAP is required — the Captivo hosted portal sends the password to the gateway, which relays a standard PAP Access-Request.

5Allowlist (walled garden) — important

In the gateway's free-URL / allowlist (walled garden) settings, allow app.captivo.io before sign-on (use the public domain, not a LAN address). The portal must load and reach Captivo before the guest authenticates.

This is the #1 cause of 'the portal opens but no SMS arrives'. The portal's JavaScript fetches the verification code from app.captivo.io, so that domain must be in the allowlist, reachable before sign-in. You do NOT need to allowlist your SMS provider's domain — Captivo sends the SMS from its own servers.

Test and troubleshooting

Connect a guest device: the branded portal appears, the guest verifies via SMS/voucher, and the gateway opens access. Auth and identity logs appear right away; to see live sessions in the dashboard, also enable RADIUS accounting to port 1813 on the gateway.

Troubleshooting — Portal doesn't open: check the external-portal URL and the allowlist (step 5). No SMS: allowlist app.captivo.io (step 5). 'Authentication failed': the NAS client IP/secret in Captivo doesn't match the gateway's RADIUS settings, or the method isn't PAP (step 3).

For product-wide problems: The portal does not open · Sign-in is rejected · Sessions do not appear