Nomadix WLAN Controllers

Download this guide ⬇

Introduction

Scope and Purpose

Thank you for purchasing the Trusted WiFi solution. This document is a hardware configuration guide describing how to setup a Nomadix WLAN Controller (either the AC-1LA physical controller or the cloud controller) for a Trusted WiFi Passpoint service.

• For more information on how to setup an end-to-end Trusted WiFi Passpoint service, please refer to the Trusted WiFi Passpoint Administration Guide.

• For complete information on how to setup a Nomadix WLAN Controller, please refer to the Nomadix Wireless Controller Web-Based Configuration Guide.

Documentation Conventions

Passpoint Overview

Passpoint – also known as Hotspot 2.0 – is an industry-wide next generation approach to public internet access driven by the Wi-Fi Alliance that brings the following benefits:

• Frictionless onboarding and roaming, thanks to a one-time registration followed by automatic access to interconnected hotspots

• More secure and private Wi-Fi connections, compared with general visitor networks

Passpoint is based on the IEEE 802.11u standard, which is a set of protocols enabling cellular-like roaming. Following the initial enrollment, frequent users such as visitors, guests or employees bypass repeated logins, forms and passwords, as their mobile devices automatically join the Wi-Fi subscriber service when they return to a venue or roam between inter-linked Passpoint enabled hotpots and providers, while being better protected against potential cyber threats.

If a device supports 802.11u and is enrolled to a service, it automatically communicates with the Wi-Fi infrastructure via the access points to discover the network SSID and connects securely to it by presenting its access credentials. Upon successful authentication, the device is provisioned with Passpoint standards-based management objects - known as Per-Provider Subscription Management Objects (PPS-MO).

GlobalReach - an ASSA ABLOY company - has been involved with Passpoint since its inception and even contributed to the creation and initial pilot testing of the standard. As a result, it is one of the few trusted worldwide experts on this topic, with a proven platform backed by real-world operational experiences at scale.

The best user experience is to offer Passpoint through a customer/brand mobile app integration, as it further simplifies the onboarding process, while incentivizing app downloads and customer loyalty, leading to further engagement and monetization opportunities. To this effect, Trusted WiFi offers a Software Development Kit (SDK) for easy app integration.

End-to-End Service Components

Implementing an end-to-end Trusted WiFi Passpoint service requires a combination of the following software and hardware components:

• Trusted WiFi Passpoint: the core services are offered and managed centrally via the Trusted WiFi Passpoint Module (hosted and operated by GlobalReach). Following an initial setup performed by the GlobalReach Operations team, Managed Service Providers (MSPs) can then add sites to customer realms and monitor the solution.

• Customer Realm: the service requires connectivity to a realm including domain, security certificate and private key, as well as the database holding the users’ Personally Identifiable Information (PII). It is the responsibility of the Identity Provider – typically the customer/brand – to make this part available.

• Mobile App: the best user experience is to offer Passpoint through a customer/brand mobile app integration. Trusted WiFi offers a Software Development Kit (SDK) for easy implementation. It is the responsibility of the app owner – typically the customer/brand – to perform the integration.

• Local Networks: the local networks must be compliant with Passpoint (Hotspot 2.0). – Most recent   Wi-Fi access points and controllers from major vendors support Passpoint today, however older models or products from more exotic manufacturers might not do. The configuration of the local infrastructure is typically handled by the Managed Service Providers (MSPs).

• User Devices: the subscribers’ mobile devices (belonging to visitors, guests, employees, etc.) must be compliant with Passpoint (Hotspot 2.0) – All recent iOS and Android-based smartphones or tablets support Passpoint today, however older models or products running less popular operating systems might not do. Laptops compatibility is also more erratic. It is therefore essential to maintain a traditional onboarding service in parallel with Passpoint to handle non-compatible devices.

High-Level Topology

The diagram below illustrates the high-level topology for the end-to-end Trusted WiFi Passpoint service:

Glossary

The following is a glossary of the most common terms used regarding this solution.

NOMADIX WLAN CONTROLLERS CONFIGURATION

Prerequisites

It is assumed the following prerequisites are met before configuring a Nomadix WLAN Controller (either the AC-1LA physical controller or the cloud controller) for a Trusted WiFi Passpoint service:

• A supported Nomadix WLAN controller, activated and licensed.

• A Trusted WiFi account with operator permissions.

• A core Trusted WiFi Passpoint service configured and tested.

• A property in Trusted WiFi with deployed Passpoint modules.

• A deployed and configured Wi-Fi network.

Note

This document focuses on a specific part of the Nomadix WLAN controller configuration only.

• Please refer to the Passpoint Administration Guide for instructions on how to configure the end-to-end Passpoint service.

• Please refer to the Nomadix Wireless Controller Web-Based Configuration Guide for complete instructions on Nomadix WLAN Controllers configuration.

Warning

• All properties must share the same NAI realm, RADIUS IP/port settings and SSID name for the Passpoint service (CustomerPasspoint).

• Each property requires a separate RADIUS secret and NAS identifier, both generated when a configuration is activated within the Trusted WiFi management platform.

Core Passpoint Settings

• Log into Trusted WiFi, then click on the Properties icon in the left menu to view the properties list.

• Select or search for the property you wish to work on. This will open its deployments page:
  

• Click on the Passpoint tile and then click on the Configuration option in the left menu to display the Passpoint settings summary as per the example below:
  

• Take note of the details for your respective installation as they will be required at a later step.

Nomadix WLAN Controllers Configuration

Wi-Fi Network

• Log into the Nomadix WLAN controller using your credentials:
  

• Click on the Config tab at the top of the screen, expand the WLAN section and select Add WiFi from the left-hand navigation menu.
  

• Click on Add WiFi/WLAN in the content area:
  

• Enter the required information, being sure to select WPA2-802.1X for encryption type. Configure any advanced settings that may be required.
  

• Click Next and specify the AP Group and other information to apply the new WLAN.

• Click Finish.
  

RADIUS

• Click on Radius Server Settings and select Add Server Group from the drop-down list:
  

• Create a group called TrustedWiFi and enter the information for the primary RADIUS server.
  

• Click Save, then click Add Server and enter details for the secondary RADIUS server and click Save again.

• Primary and Secondary RADIUS servers should have been configured as shown below:
  

• Click the X in the top right-hand corner to close the RADIUS server configuration panel. The WiFi/WLAN configuration reappears.

• Select TrustedWiFi for the Authentication Server and Accounting Server fields:
  

• Click Next. Specify the AP group and other information to apply the new WLAN if not already completed and click Finish.

Passpoint (Hostpot 2.0)

• Expand the AP section in the left-hand navigation menu and select Hotspot2.0:
  

• Enter a template name such as Passpoint and select the SSID that was created in the previous steps from the drop-down list:
  

• Expand the Advanced Settings and scroll down to the Cellular section. Complete the settings as per the description below:
  
  

  Field	Description
  Enable this DHCP pool	Select Enable
  NAI Domain	Enter the [customer domain]
  Auth Type	Select EAP-TTLS from the drop down list
  Auth Method	Select Auth-Method 2 (non-EAP Inner Authentication)
  Auth Param	Select Auth-Param 4 (MSCHAPv2)

• Scroll down to the end of the settings and click Save.

NAS ID

• Click on the Maintenance tab at in the top menu bar, expand the System section in the left-hand navigation menu and select Web Console:
  

• Using the command input box, send the sequence of commands shown below to configure the NAS-Identifier:
  
  
  Commands:

  configure
  wlan-config 1
  nas-id <nas-identifier from TrustedWiFi settings>
  exit
  exit
  wr