Creating a Hotspot Service

ZoneDirector’s Hotspot Services page can be used to configure a traditional (WISPr 1.0) hotspot service to provide public access to users via its WLANs.
Note: For information on Hotspot 2.0 WLANs, see Creating a Hotspot 2.0 Service.

In addition to ZoneDirector and its managed APs, you will need the following to deploy a hotspot:

  • Captive Portal: A special web page, typically a login page, to which users that have associated with your hotspot will be redirected for authentication purposes. Users will need to enter a valid user name and password before they are allowed access to the Internet through the hotspot. Open source captive portal packages, such as Chillispot, are available on the Internet. For a list of open source and commercial captive portal software, visit http://en.wikipedia.org/wiki/Captive_portal#Software_Captive_Portals, and
  • RADIUS Server: A Remote Authentication Dial-In User Service (RADIUS) server through which users can authenticate

For installation and configuration instructions for the captive portal and RADIUS server software, refer to the documentation that was provided with them. After completing the steps below, you will need to edit the WLAN(s) for which you want to enable Hotspot service.

ZoneDirector supports up to 32 WISPr Hotspot service entries, each of which can be assigned to multiple WLANs.

To create a Hotspot service:

  1. Go to Services & Profiles > Hotspot Services.
  2. Click Create New. The Create New form appears.
    Note: Alternatively, you can create a Hotspot service from the WLAN creation page while creating a new WLAN or modifying an existing WLAN (Wireless LANs > Edit > Type > Hotspot Service (WISPr) > Hotspot Services > Create New.)
  3. In Name, enter a name for this hotspot service. (You will need to choose this name from a list when creating a WLAN to serve this hotspot service.)
  4. In WISPr Smart Client Support, select whether to allow WISPr Smart Client support:
    • None: (default).
    • Enabled: Enable Smart Client support.
      Note: The WISPr Smart Client is not provided by RUCKUS, you will need to provide Smart Client software/hardware to your users if you select this option.
    • Only WISPr Smart Client allowed: Choose this option to allow only clients that support WISPr Smart Client login to access this hotspot. If this option is selected, a field appears in which you can enter instructions for clients attempting to log in using the Smart Client application.
    • Smart Client HTTP Secure: If Smart Client is enabled, choose whether to authenticate users over HTTP or HTTPS.
  5. In Login Page (under Redirection), type the URL of the captive portal (the page where hotspot users can log in to access the service).
  6. In Start Page, configure where users will be redirected after successful login. You could redirect them to the page that they want to visit, or you could set a different page where users will be redirected (for example, your company website).
  7. In User Session, configure session timeout and grace period, both disabled by default, and enable or disable intrusion prevention to block hotspot clients that attempt to authenticate unsuccessfully too many times.
    • Session Timeout: Specify a time limit after which users will be disconnected and required to log in again.
    • Grace Period: Allow disconnected users a grace period after disconnection, during which clients will not need to re-authenticate. Enter a number in minutes, between 1 and 144,000.
    • Intrusion Prevention: Temporarily block Hotspot clients with repeated authentication attempts (enabled by default). When this option is enabled, if the same station attempts to authenticate 10 times unsuccessfully within 300 seconds, the station will be blocked for 300 seconds. If the same user unsuccessfully attempts to authenticate 30 times within the same time period, the user will be blocked for 300 seconds.
  8. Configure authentication settings by clicking the Authentication tab.
  9. In Authentication Server, select the AAA server that you want to use to authenticate users.
    Note: Alternatively, you can create an AAA server from the Hotspot configuration page while creating a new WLAN or modifying an existing WLAN.
    • Options include Local Database and any AAA servers that you configured on the Services & Profiles > AAA Servers page. If a RADIUS server is selected, an additional option appears: Enable MAC authentication bypass (no redirection).
    • Enable MAC authentication bypass (no redirection): Enabling this option allows users with registered MAC addresses to be transparently authorized without having to log in. A user entry on the RADIUS server needs to be created using the client MAC address as both the user name and password. The MAC address format can be configured in one of the formats listed in MAC Authentication with an External RADIUS Server.
  10. In Accounting Server, (if you have an accounting server configured), select the server from the list and configure the frequency (in minutes) at which accounting data will be retrieved.
  11. In Wireless Client Isolation, choose whether clients connected to this Hotspot WLAN should be allowed to communicate with one another locally. See Advanced WLAN Options in Creating a WLAN for a description of the same feature for regular (non-Hotspot) WLANs.
  12. Configure optional Location Information settings as preferred. Enter Location ID and Location Name WISPr attributes, as specified by the WiFi Alliance.
  13. In Walled Garden, enter network destinations (URL or IP address) that users can access without going through authentication. A Walled Garden is a limited environment to which an unauthenticated user is given access for the purpose of setting up an account. After the account is established, the user is allowed out of the Walled Garden.
  14. In the Policy tab, configure Restricted Subnet settings by defining L3/4 IP address access control rules (ACLs) for the hotspot service to allow or deny wireless devices to access services or resources based on source/destination IP address, application, protocol or port number.
  15. Click OK to save the hotspot service.
  16. You may now assign this hotspot service to the WLANs that you want to provide hotspot internet access, as described in Assigning a WLAN to Provide Hotspot Service.
    Note: If ZoneDirector is located behind a NAT device and signed certificates are used with hotspot portal authentication, a static entry must be added to the DNS server to resolve ZoneDirector's private IP address to its FQDN. Otherwise, client browsers may enter an infinite redirect loop and be unable to reach the login page. Before the signed certificate gets added the client gets redirected to the IP address of the ZD instead of the FQDN.