User guide

Virtual network services (VNS): Introduction
A31003-W1010-A100-1-7619, July 2005
66 HiPath Wireless Controller, Access Points and Convergence Software V3.0: User Guide
HWC_VNSIntro.fm
Network assignment and authentication for a VNS
You can view (in the Wireless AP Configuration screen) a list of defined VNSs to which each
radio has been assigned.
In the Topology area of Virtual Network Configuration, you also define other aspects of the
VNS, such as the parameters for DHCP for IP address assignment. You might also configure
this VNS for management traffic only, or for Third-Party Access Points, or for Voice Traffic.
(These are described in detail later in this Guide.)
6.4 Network assignment and authentication for a VNS
The second step is to configure the authentication mechanism for the VNS. The authentication
mechanism depends on the network assignment. In addition, all VNS defintions can include
authentication by MAC address.
6.4.1 Authentication with SSID network assignment
If SSID was selected, there are two authentication options:
● None: The wireless device connects to the network, but can only access specified network
destinations (defined in the Non-Authenticated Filter). No authentication is performed.
● Captive Portal: The wireless device connects to the network, but can only access specified
network destinations (defined in the Non-Authenticated Filter). One of those destinations
is a web page logon screen (the portal in which he is captive), where the user must input
an ID and a password. This identification is sent by the HiPath Wireless Controller to the
RADIUS server for authentication. Four authentication types are supported by Controller,
Access Points and Convergence Software for Captive Portal:
● PAP (Password Authentication Protocol)
● CHAP (Challenge Handshake Authentication Protocol)
● MS CHAP (Windows-specific version of CHAP)
● MS CHAP v2 (Windows-specific version of CHAP, version 2)
For Captive Portal, the RADIUS server must support the selected authentication type: PAP,
CHAP (RFC2484), MS-CHAP (RFC2433), MS-CHAPv2 (RFC2759).
6.4.2 Authentication with AAA (802.1x) network assignment
If network assignment is by AAA (802.1x) with 802.1x authentication, the wireless device user
requesting network access via Controller, Access Points and Convergence Software must first
be authenticated. The wireless device's client utility must support 802.1x. The user's request
for network access along with login identification or user profile will be forwarded by the HiPath
Wireless Controller to a RADIUS server. Controller, Access Points and Convergence Software
supports these authentication types: