Specifications

Altitude 3500 Series Access Point Product Reference Guide
187
6 Configure the Key Settings area as needed to set an ASCII Passphrase and 128-bit key.
Default (hexadecimal) 256-bit keys for WP2A/CCMP include:
1011121314151617
18191A1B1C1D1E1F
2021222324252627
28292A2B2C2D2E2F
7 Configure the WPA2-CCMP Mixed Mode field as needed to allow WPA and WPA2 TKIP client
interoperation.
8 Configure the Fast Roaming (802.1x only) field as required to enable additional Altitude 35xx roaming
and key caching options. This feature is applicable only when using 802.1x EAP authentication with
WPA2/CCMP.
NOTE
PMK key caching is enabled internally by default when 802.1x EAP authentication is enabled.
9 Click the Apply button to save any changes made within this New Security Policy screen.
10 Click the Cancel button to undo any changes made within the WPA2/CCMP Settings field and return
to the WLAN screen. This reverts all settings to the last saved configuration.
ASCII Passphrase To use an ASCII passphrase (and not a hexadecimal
value), select the checkbox enter an alphanumeric string of
8 to 63 characters. The string allows character spaces.
The Altitude 35xx converts the string to a numeric value.
This passphrase saves the administrator from entering the
256-bit key each time keys are generated.
256-bit Key To use a hexadecimal value (and not an ASCII
passphrase), select the checkbox and enter 16
hexadecimal characters into each of the four fields
displayed.
Allow
WPA/WPA2-TKIP
clients
WPA2-CCMP Mixed Mode enables WPA2-CCMP, WPA-
TKIP and WPA2-TKIP clients to operate together on the
network. Enabling this option allows backwards
compatibility for clients that support WPA-TKIP and WPA2-
TKIP but do not support WPA2-CCMP. Extreme Networks
recommends enabling this feature if WPA-TKIP or
WPA2-TKIP supported MUs operate within a WLAN
populated by WPA2-CCMP enabled clients.
Pre-Authentication Selecting this option enables an associated MU to carry
out an 802.1x authentication with another Altitude 35xx
before it roams to it. The Altitude 35xx caches the keying
information of the client until it roams to the other Altitude
35xx. This enables the roaming client to start sending and
receiving data sooner by not having to do 802.1x
authentication after it roams. This feature is only supported
when 802.1x EAP authentication is enabled.