PDF(152.4 KB) View with Adobe Reader on a variety of devices
ePub(194.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(103.7 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 12, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Captive Portal Instance Association on WAP321 Access Points
The captive portal allows you to block clients connected to the WAP network. Clients see a special web page for authentication purposes before they are allowed to use the Internet normally. Captive Portal verification is for both guests and authenticated users. Captive portal makes use of the web browser and turns it into an authentication device. Captive portals are specially used at many Wi-Fi hotspots to charge users to get access to the internet. Captive portal instances are defined sets of configurations that are used to authenticate clients on the WAP network. These instances must be associated with Virtual Access Points (VAP). Different instances (maximum up to two) can be configured to respond differently to users as they attempt to access the associated virtual access point. VAPs are segmented wireless LANs in multiple broadcast domains that are wireless equivalents of Ethernet VLANs. This makes it so that multiple access points are simulated in one physical WAP device.
This article explains how to associate Captive Portal (CP) instances on the WAP321 access point.
Captive Portal Instance Association
Step 1. Log in to the web configuration utility and choose Captive Portal > Instance Association. The Instance Association page opens:
The following are the fields available under instance association.
• Network Interface — VAPs are segmented wireless LANs in multiple broadcast domains. This field shows the segmented domains; each segment is considered as different virtual access point.
• Instance Name — It shows the instance chosen for the network interface.
Step 2. Choose the instance for each VAP that you want to associate from the Instance Name drop-down list. The instance configurations will be effective and applies to the users who are in that network interface only.
Step 3. Click Save to save the changes made on the Instance Association page.