Configure the hotspot to use HotspotSystem authentication

You can configure TX64 hotspot to use HotspotSystem, a cloud hotspot service that supports various free and paid authentication methods, including social media accounts, SMS, voucher, and PayPal.

By default, the router redirects unauthenticated users to the HTML authentication page located on the router at etc/config/hotspot/login.html. You can customize the authentication page as needed, or host an authentication page on a remote server. See Customize the hotspot login page for further information.

Required configuration items

Additional configuration items

Hotspot LAN configuration:

 

  1. Sign up for an operator account. Go to HotspotSystem signup.
  2. Add a new location for the hotspot. Take care when selecting the Business Model because some options cannot be changed after you create the location. Go to Add a new location.
  3. Click Modify Hotspot Data & Settings.
  4. Click Splash Page Settings.
  5. Set Internal Login URL to http://{UAMIP}:{UAMPORT}/prelogin.
  6. Set Internal Logout URL to http://{UAMIP}:{UAMPORT}/logoff.
  7. Click Submit.

 

HotspotSystem uses various additional domains for payment processing and social media login. While unauthorized users are automatically able to access hotspotsystem.com, your hotspot configuration may require unauthorized users to have access to additional domains. These domains need to be listed by the Allowed garden > Allowed domains option. For example, this may include sites like the following:

  • PayPal and other payment processors require access to a number of domains, depending on which services you select. Contact HotspotSystem for an up-to-date list of domains that need to be whitelisted.
  • FREE Social login requires a number of domains, depending on which services you select. Refer to the following page for an up-to-date list of social login domains that need to be whitelisted: Whitelist for hotspot free social login.

You can use the Remote Webserver feature to certify and add your device to Hotspotsystem's official list of supported devices.

 

  1. Log into Digi Remote Manager, or log into the local Web UI as a user with full Admin access rights.
  2. Access the device configuration:

    1. Locate your device as described in Use Digi Remote Manager to view and manage your device.
    2. Click the Device ID.
    3. Click Settings.
    4. Click to expand Config.

    1. On the menu, click System. Under Configuration, click Device Configuration.

      The Configuration window is displayed.

  3. Create a new hotspot or Enable hotspot using the default configuration.
  4. During hotspot configuration, for Authentication mode, select HotspotSystem.
  5. Click to expand HotspotSystem.
    1. For Operator name, type the operator name that you registered with hotspotsystem.com.
    2. For Location ID, type the location ID of this hotspot. The default is 1.
  6. Click to expand Remote Webserver to redirect the hotspot to an authentication page.
    1. For FQDN, enter the Fully Qualified Domain name or IP address through which users are redirected to the hotspot splash screen, log in, or authentication page of the hotspot. The default is: https://customer.hotspotsystem.com/customer/hotspotlogin.php
    2. (Optional) For Secret, enter the secret key shared between the remote server and the hotspot. This is optional, unless you are integrating with a cloud hotspot provider.
  7. Click to expand Walled garden.

    Walled garden settings define the "white list" of domains and subnets that unauthenticated clients are able to access. Include the domain or subnet of supporting servers for payment or other external login and authentication (such as social media sites).

    • To add domains that can be accessed by the client prior to authentication:
      1. Click to expand Allowed domains.
      2. Click to add a domain.
      3. For Domain, type the hostname of the allowed domain.
      4. Repeat to add additional domains.
    • To add subnets that can be accessed by the client prior to authentication:
      1. Click to expand Allowed subnets.
      2. Click to add a subnet.
      3. For Subnet, type an IPv4 address and optional subnet mask, using the format IPv4_address[/netmask], or the keyword any.
      4. Repeat to add additional subnets.
  8. Click Apply to save the configuration and apply the change.

  1. Select the device in Remote Manager and click Actions > Open Console, or log into the TX64 local command line as a user with full Admin access rights.

    Depending on your device configuration, you may be presented with an Access selection menu. Type admin to access the Admin CLI.

  2. At the command line, type config to enter configuration mode:

    > config
(config)>

  3. Create a new hotspot or Enable hotspot using the default configuration.
  4. Set the authentication mode to hotspotsystem:
    (config)> network hotspot hotspot_name auth hotspotsystem
(config)>
  5. Configure HotspotSystem:
    1. Set the operator name that you registered with hotspotsystem.com.
      (config)> network hotspot hotspot_name hotspotsystem operator name
(config)>
    2. Set the location ID of this hotspot.
      (config)> network hotspot hotspot_name hotspotsystem location value
(config)>

      where value is any integer. The default is 1.

  6. Configure the Remote Webserver to redirect the hotspot to an authentication page.
    1. Set the Fully Qualified Domain name or IP address through which users are redirected to the hotspot splash screen, log in, or authentication page for the hotspot. 
      (config)> network hotspot hotspot_name hotspotsystem remote url value
(config)>

      where value is a FQDN: Fully Qualified Domain Name or IP address. The default is: https://customer.hotspotsystem.com/customer/hotspotlogin.php

    2. (Optional) Set the secret key shared between the remote server and the hotspot. This is optional, unless you are integrating with a cloud hotspot provider.
      (config)> network hotspot hotspot_name hotspotsystem remote secret value
(config)>

      where value is the secret key.

  7. Set walled garden settings.

    Walled garden settings define the "white list" of domains and subnets that unauthenticated clients are able to access. Include the domain or subnet of supporting servers for payment or other external login and authentication (such as social media sites).

    • Add domains that can be accessed by the client prior to authentication:
      (config network hotspot new_hotspot)> add walled_garden domains end domain_name
(config network hotspot new_hotspot)>

      Repeat to add additional domains.

    • Add IP addresses and subnets that can be accessed by the client prior to authentication:
      (config network hotspot new_hotspot)> add walled_garden subnets end value
(config network hotspot new_hotspot)>

      where value is an IPv4 address and optional subnet mask, using the format IPv4_address[/netmask], or the keyword any.

      Repeat to add additional IP addresses or subnets.

  8. Save the configuration and apply the change.
    (config)> save
Configuration saved.
>
  9. Type exit to exit the Admin CLI.

    Depending on your device configuration, you may be presented with an Access selection menu. Type quit to disconnect from the device.