Captive Access Network - Introduction
The Captive Access Network (CAN) allows each crew member/client to have a provisioned account with an associated Service Plan. The account's Service Plan is customized to match the corporate policy (Quota, Duration, Traffic Policy – for example, 10 GB/month with defined traffic policies). Devices connected to a Captive Access Network must log in through the Captive Portal before they can access the internet.
Captive Access configuration involves configuration on the KonnectOS Portal, the CAN Administration Portal and the CAN User Portal.
Configuration overview
Configure CAN in the following order:
-
KonnectOS Portal – Traffic Policies (SD-WAN > Traffic Policies): create the Network Traffic Policy for the captive network and one or more Device Traffic Policies for the plans. See CAN KonnectOS Portal Configuration.
-
KonnectOS Portal – Access Network (LAN > Access Networks): enable Captive Access Network on the Access Network and assign the Network Traffic Policy. See CAN KonnectOS Portal Configuration.
-
CAN Administration Portal – Payment GW (only for organizations using the Paywall feature): send a Stripe invite to the organization or site and wait until the connected account status is Connected. See Payment GW.
-
CAN Administration Portal – Plans: create subscription plans. For paid plans, select the Stripe account in the Stripe Account field. The plan's Device Traffic Policy / Identity Rule must match the KonnectOS Device Traffic Policy name exactly, including case. See CAN Administration Portal Configuration.
-
CAN Administration Portal – Users/Vouchers: create users or vouchers and assign plans to them. See CAN Administration Portal Configuration.
-
CAN User Portal: users connect to the Captive Access Network, are redirected to the User Portal and log in with their credentials. See CAN User Portal Configuration.
For details, see the following pages: