How To: Bypass Captive Access on a Captive Enabled Network

Keywords: EdgeOS, Captive Access Network, CAN, Bypass CAN

This How To document guides the user through the steps required to bypass captive access on a captive enabled network. Enabling Captive Access in the Access Networks allows for each crew member/user 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 – e.g., 10GB/month with defined traffic policies).

In some scenarios, the user might want to bypass the captive access functionality for few specific devices under the network. This document aims to explain how to bypass the captive access network functionality.

The user can bypass captive access in specific devices by creating and applying unique Device Traffic Policies. Follow the below steps to create and apply the device traffic policy.

Step 1: Create a Device Traffic Policy

• Login into the EdgeOS Portal.

• Click the icon at the top right corner of the homepage.

• Click Configuration Wizard.

• Click Step 4 Traffic Policies in the Configuration Wizard.

• Click the Device Tab.

• Click + Policy button to create a new device traffic policy. The Policy Name field becomes available under the Create Traffic Policy section.

• Enter the Policy Name.

• Select the required filters in the Content Filtering field if needed.

• Click Save button to save the new Device Traffic Policy.

Step 2: Apply the Device Traffic Policy to the required devices

• On the Configuration Wizard, click Step 6 General Settings.

• Expand the Device Traffic Policies section.

• The devices can be identified only by their MAC or IP Addresses.

• In the MAC/IP Address field under the Add Device section, select the required device/devices from the dropdown menu.

• Select the WAN Profile if applicable.

• In the Traffic Policy field, select the Device Traffic Policy created in Step 1.

• Click Save button to apply the Device Traffic Policy to the selected device/devices.

• Now the devices selected here will be excluded from their Captive Access functionality and will follow the newly created Device Traffic Policy.