Accor Captivnet Lite Configuration - Meraki for Captive Admin

TABLE OF CONTENTS

• Background
• Configuration Details
  • Service Tiers
    • Interim Accounting Attribute
    • Maximum Upstream/Downstream Rates
    • URL Redirect
  • Assets

Background

This document provides details of the configuration of a site using Airangel’s Captive Admin UI for the Accor Captivnet Lite solution.

Its focus is on the delta required compared to a site configuration that would be usually completed with the existing Mikrotik solution. While no Mikrotik asset will be included when creating a site using the Meraki solution, all other standard configuration areas are required (e.g. addition of Service Tiers, Portals, assets etc.).

This document will not detail all aspects of site configuration but will show the areas where modifications are required to the “usual” settings for an Accor site on Captive Admin.

Configuration Details

Service Tiers

The Meraki solution uses some additional RADIUS attributes that will need to be added to any service tiers that are associated with a site that uses a Meraki solution. These are detailed below.

Interim Accounting Attribute

The Meraki solution relies on the Acct-Interim-Interval attribute being returned in a RADIUS Access-Accept to provide the required interval for RADIUS accounting interim updates. If this attribute is not present, no interim accounting packets are sent by the Meraki cloud to the Airangel RADIUS servers.

The minimum value allowed for this attribute is 300 seconds (5 minutes). 

Maximum Upstream/Downstream Rates

The Meraki solution will only enforce per session up/down data rates if it receives the Maximum-Data-Rate-Upstream and Maximum-Data-Rate-Downstream. These are not the attributes that are usually used for per-session bandwidth control.

These attributes may be added to existing service tiers and will co-exist with other, existing bandwidth control attributes that are used for other vendor solutions (e.g. Mikrotik).

URL Redirect

Although not used at all sites, some Accor sites use a local over-ride of the post authentication destination using the “Redirect URL” attribute. This has been tested and verified as working as expected with the Meraki solution.

Assets

Each Meraki access point (AP) used on the site must be added to the list of site assets in Captive Admin.

Each AP must be assigned the following fields:

• Name

• Mac Address

• Device type: Other

• Vendor: Meraki

Here is a sample asset for reference:

Note that the Captive Admin asset import feature can be used to import APs in a CSV-format file. Here is a sample CSV file for mass import operations: