Gateway Configuration
From WirelessOrbit
If you're trying to configure a gateway in the list of supported hardware just follow the configuration instructions on the relevant page.
This page is intended to give an overview of things you can try if you're trying to get unsupported hardware working.
Contents |
Overview
Wireless Orbit can, at least in theory, work with virtually any wireless gateway or router that supports authentication via an external RADIUS server and mechanism for handling captive portal authentication. This usually involves getting a couple of things done:
- Pointing the gateway at Wireless Orbit's RADIUS servers for authentication
- Pointing the gateway's captive portal mechanism at Wireless Orbit's login portal server for the login page
- Making sure the Control Center knows what kind of login page to use
RADIUS Settings
This is usually pretty straightforward if the gateway supports RADIUS at all. You typically need to:
- Give the IP address of the RADIUS server: 69.36.234.20
- Give the shared secret key: you choose this yourself and enter the same value in the RADIUS profile in the Control Center
- You may need to give an authentication port: 1812
- You may need to give an accounting port: 1813
Captive Portal Settings
The way captive portals are handled varies a lot from vendor to vendor. You might have to fiddle around with things some, but usually you'll need to:
- Enter a URL for an external login page: the URL is given in the gateway details page in the Control Center, and will be unique for each gateway
- You may need to add portal.wirelessorbit.com to the walled garden settings (to allow users to access the login page)
- You may need to add additional walled garden entries for your payment gateway
Control Center Settings
The only special thing you may have to do in the Control Center (beyond what's usually involved with configuring a new gateway in the Control Center) is try multiple gateway types.
The gateway type controls a couple of things. The most important is the construction of the login form used by the captive portal. Different vendors use different variables in the login form, and if the variables sent by the gateway don't match what the Control Center is expecting, it won't work.
If you're not sure what to try, a good place to start is one of the open source/free gateway types---like DD-WRT, ChilliSpot, or Generic WISPr. This is because they use common captive portal settings. If you try one of these and it works with hardware that isn't on the supported hardware list, let us know.