
1 – CLI Overview
100-8005-101G Airborne™ Product Family CLI Reference Guide Page 15
Quatech, Inc. Confidential
LEAP
In order to function properly, a RADIUS server configured for LEAP containing
usernames/passwords, and an Access Point that supports LEAP, must be available. The
RADIUS server username and password must match the user-leap and pw-leap command
values configured on the WLN.
1.8.5 System Implementation Considerations
The WLN must be in infrastructure mode for WPA-PSK or LEAP to operate properly. A WLN
configured for WPA-PSK requires a connection to an AP with WPA-PSK enabled. A WLN
configured for LEAP requires a connection to an AP with LEAP enabled and connected to a
RADIUS server to provide authentication.
Until the WLN is authenticated by either the WPA-PSK enabled AP or the RADIUS server, no IP
network communication can proceed.
Symptoms of an unauthenticated client include:
A WLN with serial-default set to “PASS” will not connect to the network client.
A WLN configured for DHCP will not obtain host configuration from the DHCP server;
therefore, the IP address will remain 0.0.0.0.
The Link LED turns on when 802.11 association completes. However, if the 802.1X
authentication fails, the WLN becomes disassociated by the AP, the Link LED turns off
and the RF_ACT LED will blink rapidly. In effect, the Link LED will blink slowly as the
process repeats.
The WLN will not respond to discovery requests.
Once the WLN is authenticated, additional impacts include:
Roaming
A WLN configured for WPA-PSK can only roam to APs that have WPA-PSK enabled in
the same ESS.
A WLN configured for LEAP can only roam to APs that support LEAP, roaming, and are
connected to the same RADIUS server.
Data Throughput and Latency
Round trip latency may increase and overall throughput may decrease, due to the
additional steps to encrypt or decrypt data.
Re-Keying
The session key may expire and the authentication process will be executed again
causing streaming data to stop until a new key is authorized.
Comentarios a estos manuales