Set up InHand Networks routers with MyWiFi

What you'll need

• An InHand Networks router with Wi-Fi and captive portal support: InRouter IR300/IR600/IR900 series, EdgeRouter ER605/ER805, or FWA12. Use current firmware; menu names below vary a little between models and firmware versions.
• Admin access to the router's web interface, or to InCloud Manager for cloud-managed ER-series routers
• The router's MAC address (printed on the label, and shown on the router's status page)
• A MyWiFi location (one physical venue in MyWiFi, with its own devices, campaigns, and guest data) already created
• MyWiFi's RADIUS server IP addresses and shared secret (RADIUS is the protocol your router uses to ask MyWiFi whether a guest may go online), from your MyWiFi device registration screen

Confirm on your router: InHand names these settings a little differently by model and firmware (for example "Portal", "Captive Portal" or "Wi-Fi Portal", and "External" or "Third-party" portal). The menu and field names below are a guide, so match them to what your router shows. If a field isn't there, contact MyWiFi support with your model and firmware version.

Steps

1. In the MyWiFi dashboard, go to Devices and click Add Device.
2. Select the Location, name the device, and under Select Your Hardware choose InHand Networks.
3. Enter the router's MAC address and click Confirm Setup. MyWiFi uses this MAC to find the location and campaign whenever a guest joins.
4. On the router, open the Wi-Fi portal (captive portal) settings for the guest SSID (the WiFi network name guests see when connecting) and set the portal type to External (confirm on your router; some firmware calls it "Third-party").
5. Paste this as the external portal URL, with your router's MAC address in place of the example: https://portal.mywifi.io/?vendor=inhand&device=00:18:05:AA:BB:CC. If you resell under your own portal domain, use that domain instead of portal.mywifi.io. Keep vendor=inhand exactly as written; it tells MyWiFi how to hand the guest back to an InHand router.
6. Set the portal's authentication to RADIUS. Enter MyWiFi's primary and secondary RADIUS server IPs, authentication port 1812, accounting port 1813, and the shared secret. Turn on accounting so session time and data usage show up in MyWiFi. If there is a UAM secret field (confirm on your router), leave it blank unless MyWiFi support gave you one.
7. Add MyWiFi's domains to the portal's walled garden (the short list of domains guests can reach before logging in, sometimes called the whitelist or free access list): mywifi.io, securewifilogin.com, cloudfront.net and amazonaws.com. If your splash page offers Facebook, Google or another social login, add that provider's domains too.
8. Save and apply the settings (in InCloud Manager, push the configuration to the router).
9. Test it: connect a phone to the guest SSID. Your MyWiFi splash page (the branded login page guests see) should open, and after logging in the phone should get internet access.

Best practice: after a guest logs in, MyWiFi sends their browser back to the router's own address on your guest network to finish granting access. That address has to be a local one (for example 192.168.2.1), which is the InHand default. If you changed the router's LAN to a public IP range, guests will see a login error at the last step.

If the splash page shows the default campaign instead of the one scheduled for this location, check that the MAC in the portal URL matches the one you entered in MyWiFi, character for character.

Related articles

• Set up Cradlepoint NetCloud with MyWiFi
• Generic RADIUS / WISPr