Cisco Meraki

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 Cisco Meraki 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 Cisco Meraki, please refer to the vendor’s original documentation.

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.

CISCO MERAKI CONFIGURATION

Supported Versions

This document is based on Cisco Meraki MR 30.7.

Prerequisites

It is assumed the following prerequisites are met before configuring Cisco Meraki for a Trusted WiFi Passpoint service:

• A supported Cisco Meraki account 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 Cisco Meraki 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 original Cisco Meraki documentation for complete instructions on Meraki 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.

Cisco Meraki Configuration

SSID & Access Control

• Log into the Cisco Meraki Dashboard with your credentials to display the page below:
  

• On the left-hand side menu items, click on Wireless - > SSID. Under an unused SSID click edit settings. The following screen will appear:
  

• Complete the fields, as per the description below:

  Field	Description
  Basic Information
  SSID (name)	Provide an SSID name.
  SSID Status	Select the Enabled option for SSID status.
  Security	Select Enterprise with radio box and select my RADIUS server.
  Wi-Fi Personal Network (WPN)	Select Disabled.
  WPA encryption	Select WPA2 only.
  802.11w	Select the Disabled (never use) radio button.
  Mandatory DHCP	Select Disabled.
  Splash page	Select None (direct access).

• Scroll down to RADIUS.

• Under RADIUS servers, click Add Sever to configure your Authentication RADIUS settings. You will need to add two servers, for Primary and Secondary settings.
  

• Complete the fields, as per the description below:

  Field	Description
  Primary Sever
  IP Addresses	Enter the <Primary RADIUS IP> from Trusted WiFi.
  Port	Enter the < RADIUS Authentication Port> from Trusted WiFi.
  Shared Secret	Enter the < RADIUS Shared Secret> from Trusted WiFi.
  Secondary Server
  IP Addresses	Enter the <Secondary RADIUS IP> from Trusted WiFi.
  Port	Enter the < RADIUS Authentication Port> from Trusted WiFi.
  Shared Secret	Enter the < RADIUS Shared Secret> from Trusted WiFi.

• Click on Done.

• Under RADIUS accounting servers, click Add Sever to configure your RADIUS Accounting settings. You will need to add two servers for both Primary and Secondary settings.
  

• Complete the fields, as per the description below:

  Field	Description
  Primary Sever
  IP Addresses	Enter the <Primary RADIUS IP> from Trusted WiFi.
  Port	Enter the < RADIUS Authentication Port> from Trusted WiFi.
  Shared Secret	Enter the < RADIUS Shared Secret> from Trusted WiFi.
  Secondary Server
  IP Addresses	Enter the <Secondary RADIUS IP> from Trusted WiFi.
  Port	Enter the < RADIUS Authentication Port> from Trusted WiFi.
  Shared Secret	Enter the < RADIUS Shared Secret> from Trusted WiFi.

• Scroll Down to Advanced RADIUS Settings.

• Under NAS ID Category 1, select Custom from the drop down.

• Enter the NAS ID from the Trusted WiFi configuration settings.
  

• Click Save on the bottom of the screen.

Passpoint (Hotspot 2.0)

• Click on the Wireless > Hotspot 2.0 on the left of the screen to display the page below:
  

• Complete the fields, as per the description below:

  Field	Description
  Hotspot 2.0	Select Enabled from the dropdown.
  Operator name	Enter an operator name.
  Venue name	Enter a venue name.
  Venue type	Select a venue type from the drop-down.
  Network type	Select a network type from the drop-down.
  Domain list	Enter the domain as shown in your configuration in Trusted WiFi e.g. customer.cloud.gobal
  Roaming Consortium OIs	Leave blank.

  
  

  

• Click on Create realm. The following screen will display:
  

• Complete the fields, as per the description below:

  Field	Description
  Format	Select 0.
  Name	Enter the name realm. e.g. customer.cloud.global
  Method ID	Select 21.EAP-TLLS from the drop-down.
  Authentication Methods	Select PAP, MSCHAP and MSCHAPV2.

  

• Click on Create realm.
  

• Click Save changes.