Cisco Cisco Aironet 350 Wireless LAN Client Adapter
2
Release Notes for Cisco Aironet Client Utilities, Version 1.5.x for Linux
OL-1347-01
System Requirements
This release introduces the new features discussed inthe “New Features” section on page 3 and resolves
the caveats listed in the “Resolved Caveats” section on page 5.
the caveats listed in the “Resolved Caveats” section on page 5.
System Requirements
Release 1.5.x of the Cisco Aironet client utilities can be used with only Cisco Aironet 340, 350, 4500,
and 4800 Series Wireless LAN Adapters (PC cards, LM cards, and PCI client adapters) and Linux kernel
version 2.2.xx or 2.4.xx.
and 4800 Series Wireless LAN Adapters (PC cards, LM cards, and PCI client adapters) and Linux kernel
version 2.2.xx or 2.4.xx.
Important Notes
Please read the following important notes before installing and using the latest client utilities.
Remove Old Files Before Running ACU Version 1.5.6
The /etc/ethX.cfg files in previous versions of ACU are not compatible with version 1.5.6 and can cause
problems if ACU finds them and attempts to load them. Please remove any old /etc/ethX.cfg files prior
to running ACU version 1.5.6 for the first time.
problems if ACU finds them and attempts to load them. Please remove any old /etc/ethX.cfg files prior
to running ACU version 1.5.6 for the first time.
EthX.cfg File Is Preconfigured for 30-mW Operation
The supplied default ethX.cfg file contains a power setting of 30 mW for compatibility between Cisco
Aironet 340 and 350 Series Wireless LAN Adapters. For 350 series client adapters, use ACU if you want
to set a higher power level.
Aironet 340 and 350 Series Wireless LAN Adapters. For 350 series client adapters, use ACU if you want
to set a higher power level.
Volatility of LEAP Credentials
If you use LEAP authentication, be advised that the LEAP credentials (username and password) are not
stored in the /etc/ethX.cfg files. Even though the client may be configured through the bcard utility to
associate to a LEAP-enabled access point, the client will not LEAP authenticate. To authenticate, either
manually restart ACU and enter your LEAP credentials via the Commands > Set LEAP Information
menu option or use one of the new LEAP credential utilities.
stored in the /etc/ethX.cfg files. Even though the client may be configured through the bcard utility to
associate to a LEAP-enabled access point, the client will not LEAP authenticate. To authenticate, either
manually restart ACU and enter your LEAP credentials via the Commands > Set LEAP Information
menu option or use one of the new LEAP credential utilities.
Note
One possible solution is to set the LEAP credentials via the bcard and leapscript utilities.
To do so, add a line after the call to bcard that calls leapscript with your username and
password.
To do so, add a line after the call to bcard that calls leapscript with your username and
password.