ExtremeControl With WiNG 5.8
ExtremeControl With WiNG 5.8
Contents
Initial
Overview
This section provides a brief overview of the traffic flow and RADIUS authentication. The
figure below shows the components in use and how authentication flows through the
solution.
Note
In addition to the steps created in this guide, it is also recommended to have IP helper addresses
pointed to the Access Control Engine and SNMP Read-Only credentials configured on the router
which Access Control can query to assist with IP resolution.
SNMP configuration is accomplished by logging into the wireless controller and navigating
to Management tab under Configuration. In the Management Policy section select the
the management policy in use and select Edit:
In the management policy, select the SNMP tab. Ensure that SNMPv3 is enabled. Then
select the SNMPv3 Users and verify the settings so that they can be used when configuring
Access Control. If desired, change the password from the default, Once complete, if any
changes were made, select OK followed by a Commit.
In the RADIUS Authentication tab, select the Add button to create a new RADIUS Server.
In the Authentication Server window, use the following settings in addition to the defaults
that are populated. Select OK and then Exit when the settings are complete.
Secret: ETS_TAG_SHARED_SECRET
Select the RADIUS Accounting tab and add a RADIUS Accounting Server. Use the default
settings with the exception for the Host IP, Secret, and Request Proxy Mode as with the
Authentication Server. Select OK and Exit when the settings are complete.
Finally, select the Settings tab of the AAA policy. In this screen, a few items need to be
adjusted. Once completed, select the OK button followed by Exit and then Commit.
Once completed, select the OK button followed by Exit and then Commit.
Application Policies
An application policy can be created to control layer 7 applications such as streaming video
applications, social media, and peer to peer applications. To create such policies, navigate
to the Network tab under Configuration. Then select the Application Policy section. Select
the Add button to create a new Application Policy.
Name the new application policy and create the types of Application Policy Rules that are
desired. Each Application Policy Rule can be added by creating new rows. Once the rules
are created, select OK and Exit. Commit the changes when complete.
In the new IP Firewall Policy, assign a name that can be used for the Wireless Client Role.
Create individual ACL rules that will be assigned to match the desired level of access. The
rules can be re-ordered with drag-and-drop if desired. Once complete, select the OK button
followed by Exit. Then select the Commit button.
Note
Currently a bug exists in WiNG 5.8.4 where the IP Firewall Policy can be created that contains a
space but If it does contain a space, the firewall policy will not be applied. This is targeted to be
fixed in WiNG 5.8.6.
Name the role policy, then press OK. Next, select the Roles tab to start creating the roles.
In the new Role, enter a name and select OK. In the Match Expressions field, change the
Group Configuration to create an Exact match of the name of the Filter-Id that will be
received from Access Control. For instance, if the Guest Access role is being sent back, the
matching configuration should match the screenshot below. Also note that for different roles,
the Role Precedence needs to be different. Once that is set, select the Firewall Rules tab
to assign the access.
In the Firewall Rules tab, the previously created Application Policy and IP ACL rules can be
be assigned as well as a VLAN override if desired. Once the firewall rules are complete,
select the OK button followed by Exit.
Repeat this process for any additional roles that need to be created. Commit the changes
once complete.
In the Application Visibilty (AVC) section, enable the checkbox for Enable dpi and select
OK followed by Exit and
To create the captive portal configuration, select the Services section of Configuration.
Then select the Captive Portals section. Select Add to create a new configuration.
In the new Captive Portal policy, select Centralized Controller for the Captive Portal Server
Mode. In the Captive Portal Server Host field, specify a non-existant server host where the
web request would typically be sent. In the Access field, select No authentication required
for the Access Type. Press OK to save the new Policy.
While still in the newly created Captive Portal Policy, scroll down to DNS Whitelist and
select the Add button.
Create entries in the DNS whitelist for both the IP address and hostname of the Access
Control Engines used on the network. Once added, select the OK and Exit buttons.
In the Captive Portal Policy, select the newly created DNS Whitelist from the dropdown
menu and then select OK followed by Commit.
The final step is to assign the new Captive Portal policy to the Device Profiles in use. To do
this, select the Profiles tab under Configuration and then navigate to the profile to be
modified. Select the Services tab of the profile and then select the checkbox next to the new
Captive Portal Policy. Once complete, select the OK button followed by Commit.
In the new WLAN screen, create the basic configurations required such as the SSID name,
Bridging Mode and VLAN Assignment. Then enable the Allow RADIUS Override
checkbox and select the OK button.
Next, navigate to the Security section of the WLAN. If using 802.1X select EAP. Otherwise,
select MAC for the authentication type. Once the authentication type is set, select the AAA
Policy that was created from the drop down list. Next, select the checkboxes next to
Captive Portal Enable and Captive Portal if Primary Authentication Fails. From the
Captive Portal Policy drop down list select the previously created Captive Portal Policy. If
the encryption methods need to be set for the SSID type, scroll further down the page and
select the appropriate settings for the type of SSID. Select the OK button to continue.
Next, select the Accounting section of the WLAN. Select the checkbox for Enable RADIUS
Accounting and ensure that the AAA Policy previously created is selected. Select the OK
button to continue.
The last configuration step for the WLAN is in the Advanced section. Select the checkbox
next to RADIUS Dynamic Authorization and then select OK followed by Exit. Then
Commit the configuration.
The last configuration step for the Wireless Network is to assign it to the AP Radios.
Navigate to the appropriate Profile and expand the Interface section to select the Radio.
Select a radio and then the Edit button.
In the Radios window, select the WLAN Mapping / Mesh Mapping tab. Select the newly
created WLAN and then the arrow to map it to the radio. Select the OK button followed by
Exit and repeat the process for any additional radios.
Note
This section assumes that the Access Control Engine is already configured and added to Access
Control. It also assumes that Guest Registration is already enabled.
Next, select CLI Credentials in the Profiles tab and create a new CLI configuration to access
the WiNG Controller in the event that scripts are used in ExtremeManagement. If no scripts
are going to be used, this step can be skipped.
With the SNMP Credentials and CLI Credentials configured, create a Profile to map them
together. Ensure that the SNMP settings are configured for AuthPriv for the SNMP Read,
Write, and Max Access.
In the Add Switches dialog, if the wireless controller hasn’t been added to
ExtremeManagement yet, select the Add Device button to add the IP address of the
wireless controller and the SNMP Profile to use for communication.
Once the wireless controller is added to ExtremeManagement, select the wireless controller
from the device list. Some configurations of the dialog are automatically populated. Select
the Access Control Engine from the Primary Engine drop down list. If there is more than
one Access Control Engine, do the same for the Secondary Engine. Set the RADIUS
Attributes to Send to Filter-Id & Custom Attribute and then set the Policy Domain to Do
Not Set.
Once RADIUS Accounting is enabled, change the Auth. Access Type back to Manual
RADIUS Configuration then select the Advanced Settings button.
In the Advanced Switch Settings dialog, the Reauthentication Type must be modified.
From the drop down list select RFC3576 - ExtremeWireless WiNG. If the setting is not
currently available, see Appendix A to create the Reauthentication Configuration.
The final settings should look similar to the below image. Once complete, press the Save
button.
Select the Rules section in the Access Control Configuration. Find the Unregistered rule
and then select the Unregistered Accept policy.
In the Edit Policy Mapping dialog, there is a field available for Custom 1. The following
attribute format should be used to instruct the controller to redirect to the Access Control
Engine:
Custom 1: cisco-avpair=url-redirect=http://<AccessControlEngineIP>:80/main
For example, if the Access Control Engine IP address is 10.120.85.81, the attribute is:
Custom 1: cisco-avpair=url-redirect=http://10.120.85.81:80/main
If HTTPS and a fully qualified domain name are used on the Access Control Engine, the
attribute is:
Custom 1: cisco-avpair=url-redirect=https://eac-engine-poc.cse.ets.com:443/main
Once the configuration for each Accept Policy is complete, Enforce to the Access Control
Engines.
Part 3 – Validation
Validation of the configuration is completed by connecting a device to the SSID that was
created and verifying that network connectivity is established. Opening a web page on the
client should redirect to the captive portal provided by the Access Control Engine. Once the
registration is complete and the user selects the Complete Registration button, the user
will be seamlessly moved to a new role.
When looking at ExtremeControl, the end system information should also be populated with
detailed end system information.
When looking at the End-System Details for a device that has not yet gone through
registration, the RADIUS attributes that were configured should be shown.
In the End System Events for the device, the audit trail of the states and access assigned
will be shown.
In the wireless controller, the role application can be verified by locating the wireless client
and selecting the Details. The role will be displayed in the window.
Once in NAC Manager, right-click on the All Access Control Engines group and select
Appliance Settings Reauthentication.
In the new Switch Reauthentication Configuration window, select Manage RFC 3576
Configurations.
Use the following settings in the new RFC 3576 Configuration and then press OK to save
the configuration.
Note
Due to a bug in the current WiNG 5.8.4, CoA cannot be used to seamlessly transition the user
between states. Instead, the Supports Change of Authorization checkbox should be disabled so
that Disconnect Messages are used. This is targeted to be fixed in WiNG 5.8.6.
Additional Attributes
Acct-Session-Id: Enabled
Custom Attributes: Cisco Wired Reauthenticate Host
Press OK to save the RFC 3576 Configurations. If the sysObjectId of the wireless controller
is known, it can be mapped to the reauthentication configuration in the window below.
Otherwise select Cancel and the configuration can be statically mapped in the Advanced
Settings of the Add Switch dialog when adding the wireless controller to Access Control.
Enforce the configuration once complete.
Revision History