What you'll need
- Admin access to your ADTRAN Bluesocket vWLAN controller
- Note: this product line is end-of-life and discontinued by ADTRAN. This guide is for supporting existing deployments — MyWiFi does not recommend Bluesocket vWLAN for new installs, and ADTRAN's own support documentation for it is largely inaccessible without a partner account.
- The MAC address of every access point you plan to connect — each one must be pre-registered before login will work (see below)
- A MyWiFi location already created, so you have a splash page URL and a RADIUS shared secret to enter
Steps
- On the vWLAN controller, create two RADIUS accounting servers (port 1813, interim updates every 300 seconds) and two RADIUS authentication servers of type RadiusWebAuthServer (port 1812) pointing to MyWiFi's RADIUS IP and shared secret — set one as primary (highest precedence) and one as secondary (lowest).
- Create a Captive Portal Login Form. Enable Redirect Clients To An External URL and set the Base URL to your MyWiFi splash page URL. Leave Double Encoding of URI Parameters unchecked.
- Create an Un-registered Role that allows traffic to MyWiFi's walled-garden domains, and a Guest Role with the MyWiFi success URL set in the URL Redirect field, plus whatever bandwidth shaping you want applied to guests.
- Create an SSID using Open System / Captive Portal Authentication, assign the Un-registered Role, and link the Login Form you created.
- Register every access point's MAC address with MyWiFi support before going live.
- In the MyWiFi dashboard, go to Devices and click Add Device.
- Select the Location, name the device, and under Select Your Hardware choose ADTRAN Bluesocket vWLAN.
- Enter your vWLAN connection details as prompted and save.
Best practice: register every AP's MAC address with MyWiFi support before you try to go live. If an AP's MAC isn't registered, the vWLAN controller rejects the login handshake outright with a "hotspot deactivated" error — and that's a bad thing to discover in front of a customer. Also confirm the controller has a valid (non-self-signed) SSL certificate, since login credentials are passed to it as a browser redirect and a certificate warning will break the flow.
Comments
Please sign in to leave a comment.