System information

roam will occur because of client movement. If an AP does fail and the routes are configured in
the manner described above, a short interruption of service could be observed. (Please see
section 4.6.1 for a description of how to demonstrate a roam without the chance of a routing loop).
4.2.3. Set the MTU Size
Configure the interface MTU size appropriate throughout the network to support the larger
frames potentially involved in L3 Tunneling.
4.3. Configure WLAN Settings
Configure the WLAN parameters to support the 3 Tunneled SSID Networks on both Unified
Switch1 and Unified Switch2. Configure the “Guest” SSID to use no security, “D-LINK-NET1”
to use WPA2 (see below), and “D-LINK-NET2” to use Static-WEP. Provide the L3 Tunnel
Subnet addresses in the configuration.
4.3.1. WPA2 Configuration
To support WPA2, enable “wpa-enterprise” security mode, configure the WPA Ciphers to use
TKIP and CCMP, and include WPA version WPA2. Furthermore, configure the IP address and
configured secret for the Radius server in the AP Profile (192.168.4.1). You will also need to
appropriately configure your client to support WPA2 which might require a client OS update.
4.3.2. Configure Discovery
Configure WLAN Discovery parameters on Unified Switch1 and Unified Switch2. Use IP/L3
Discovery on Unified Switch1 and/or Unified Switch 2 to discover the other peer switch across
subnets (in other words, add the loopback address of Unified Switch 2 into the IP discovery list
for Unified Switch 1). Use L2/VLAN Discovery on Unified Switch 1 and Unified Switch 2 to
discover the APs on VLANs 101 and 102 respectively (in other words, add VLAN 101 to the L2
discovery list on Unified Switch 1 and VLAN 102 to the discovery list on Unified Switch 2).
4.3.3. Connections
Connect devices and verify that APs move to managed state. You will need to add the APs MAC
addresses into your local AP database.
4.4. Configure the RADIUS Server
Since WPA Enterprise (WPA2) uses a RADIUS server to authenticate clients, you must configure
a client entry for the AP, which makes requests to the RADIUS server on behalf of the clients,
and an entry for each of the users. In this example, you only add one user entry to the RADIUS
database.
This configuration is applicable to only FreeRadius ( http://www.freeradius.net/
) radius server.
The configurations in this section involve the following two files:
• C:\Program Files\FreeRADIUS.net-1.1.1-r0.0.1\etc\radd\client.conf
• C:\Program Files\FreeRADIUS.net-1.1.1-r0.0.1\etc\radd\users