WildPackets - Atheros Wireless LAN Adapter 4.2.1 Driver Readme
This document provides information specific to the WildPackets driver used for Atheros
AR5001, AR5002, AR5004, AR5005 and AR5006 chipset-based adapters. This driver is for use
with AiroPeek and OmniPeek, hereafter collectively referred to as Peek in this document.
For the most up-to-date information on supported wireless adapters and drivers, please
refer to the Supported Hardware page for your Peek product, which can be found at
http://www.wildpackets.com/support/product_support/overview
IMPORTANT!
Windows 95, 98, ME and NT4 are not supported.
Some adapters require the use of a previous version of our driver. Please
visit our website at
http://www.wildpackets.com/support/omni/omnipeek_enterprise/wireless to
check if this applies to your particular adapter.
In order to capture on all available channels for network analysis, both bands,
802.11a and 802.11b/g, must be enabled. Some Original Equipment Manufacturer
(OEM) wireless configuration utilities offer the option to disable either the
802.11a or the 802.11b/g band. If you choose to disable either band, Peek will
not capture packets on any of the channels for the band you disabled.
Ensure that no OEM wireless configuration utility is installed. This type of utility
is sometimes installed when you install the OEM driver provided with the adapter.
For Windows XP users, we recommend using the operating system's built-in wireless configuration
dialogs (e.g. Zero Config).
OEM wireless configuration utilities that are sometimes required for network
services are not supported because these utilities usually require OEM-specific
support in the driver. The WildPackets driver is based on a generic Atheros
driver and does not have any OEM-specific support. There are two workarounds.
The first is to reinstall the OEM driver whenever network services are needed.
The second is to use two wireless adapters, one adapter for network services and
one adapter for wireless packet capture.
By default, when building its list of keys used for WPA/PSK security, the driver ignores
all EAPOL-Key packets received with an error. There is an option provided in the
card's Device Manager advanced properties to ignore these packets. While turning
this setting OFF will increase the chances of getting the keys to decrypt WPA encrypted packets, it also makes
it possible to get invalid keys which will not decrypt data properly.
Installation
Go to the appropriate section for your operating system for detailed WildPackets
driver installation instructions. Please check the Operating System support
requirements for your Peek product, as the Peek product using this
driver may not be supported on the same operating systems as the driver
itself.
Uninstallation
To uninstall the WildPackets version of the driver, simply reinstall the OEM driver.
International Support
In order to capture packets in a regulatory domain (i.e. country) different than the
one the adapter was bought in originally, you must change the "Peek Country" code being
used by the adapter.The "Peek Country" code is only used by Peek and does not have any effect on the country code used for
network services.
To change the adapter's "Peek Country" code on Windows XP, follow these steps:
- Stop all captures and quit Peek.
- Open the Network Connections Control Panel.
- Locate your wireless network adapter, right-click on it, and select Properties.
- Click on Configure, then the Advanced tab.
- Change the value of the "Peek Country" to the desired country.
- Click on OK and close all the windows you just opened.
- Restart Peek, you should now have access to a different set of channels.
To change the adapter's "Peek Country" code on Windows 2000, follow these steps:
- Stop all captures and quit Peek.
- Go to Start Menu | Settings | Network and Dial-up Connections.
- Locate your wireless network adapter, right-click on it, and select Properties.
- Click on Configure, then the Advanced tab.
- Change the value of the "Peek Country" to the desired country.
- Click on OK and close all the windows you just opened.
- Restart Peek, you should now have access to a different set of channels.
New Features and Enhancements
- Added support for cards based on the Atheros AR5005 chipset.
- Added support for cards based on the Atheros AR5006 chipset.
Known Issues
- Network services may not be restored after quitting Peek. This problem
is more prevalent on Windows 2000 but will sometimes occur on
Windows XP. This problem is very likely to occur when WEP (Wired Equivalent
Privacy) is disabled or when using WPA. The first workaround is to disable the wireless adapter,
then re-enable it. The second workaround is to eject the wireless adapter, then
reinsert it. The final workaround is to reboot the computer.
- Correct channel selection may not occur for some adapters when selecting
a channel by BSSID or ESSID.
- 802.11g channel 6 turbo mode is not supported.
- Atheros Super G™ and Super AG™
modes are not supported.
- Channel 161 high bandwidth captures, such as streaming video, may be
intermittent or may stop.
- For additional known issues information, including support for
particular adapters, please visit our website at
http://www.wildpackets.com/support/omni/omnipeek_enterprise/wireless.
Capturing Wireless Packets
To capture wireless packets using wireless Peeks other than OmniEngines,
such as AiroPeek NX or OmniPeek Enterprise, follow these steps:
- Launch Peek and select your wireless adapter as the Monitor adapter if
asked. If not asked, select Monitor/Select Monitor Adapter from the menu.
- Select your wireless adapter from the list on the Adapter tab.
- Select the 802.11 tab, click on the Number radio button, and choose the
appropriate channel from the drop-down list.
- If you are using WEP or WPA, click Edit Key Sets... and then Insert....
- Name the key set, select the appropriate encryption algorithm, and enter the
information in the appropriate key field(s).
- Click OK to save the Key set, and then OK to close the window.
- Select your key set from the drop-down list and then click OK to
accept the 802.11 settings.
- You can now open a new capture window by clicking on the 'New Capture'
button from the Start page, or select File/New from the menu.
To capture wireless packets using OmniEngines, follow these steps:
- Connect to your OmniEngine.
- Select 'Captures' under the desired Remote Engine in the
left pane.
- Click on the 'Insert' icon in the tool bar to create a new
capture.
- Click on 'Adapter' in the left pane of the Capture Options window.
- Select your wireless adapter from the list in the right pane.
- Click on the 'Adapter Options' icon in the tool bar.
- From the 802.11 tab, click on the Number radio button and
choose the appropriate channel from the drop down list.
- If you are using WEP or WPA, click Edit Key Sets... and then Insert....
- Name the key set, select the appropriate encryption algorithm, and enter
information in the appropriate key field(s).
- Click OK to save the key set, and then OK to close the window.
- Select your key set from the drop-down list and then click OK to
accept the Adapter Options settings.
- Verify that all other capture options are properly configured and click on OK to
accept the settings.
- When the capture window opens, click on the Start Capture button to start
the remote capture.
Card Configuration Options
The WildPackets driver provides additional configuration options which are
accessed via the Advanced tab when viewing the properties of the card.
The additional options are:
- Peek Country: Specifies the country code of the card when the card is
being used by Peek. This option allows the country code of the card to be
overridden, providing access to a different set of channels than are normally
available. The default is '[From the card]'.
- Peek Ignore Error EAPOL-Key: Specifies whether EAPOL key packets that are
in error, for example FCS error, are ignored when calculating Group Temporal
Keys (GTK) and Pair wise Transient Keys (PTK). The default is to ignore these
packets.
- Peek Max GTK: Specifies the maximum number of Group Temporal Keys that the
driver can store for decryption use. This option is for WildPackets use. The default is 4.
- Peek Max PTK: Specifies the maximum number of Pair wise Transient Keys that
the driver can store for decryption use. This option is for WildPackets use. The default is
256.
INSTALLATION
IMPORTANT!
You must first install and test the adapter with the OEM driver. Do
not install the WildPackets driver until the adapter is functioning
properly on your network using the OEM driver.
Install the Peek product if it's not already installed.
To install the WildPackets driver, follow these steps:
- Open the Network Connections Control Panel.
- Select the appropriate connection, right-click on it, and select
properties.
- Click on Configure, the Driver tab, and then on Update driver.
- Click 'No, not this time', then Next, if your version of Windows prompts
you to connect to Windows
Update to search for software.
- Click on 'Install from a list or specific location (Advanced)',
and then on Next.
- Click on 'Don't search. I will choose the driver to install.' and
then on Next.
- Click the Have Disk button.
- If you received this driver independently from the program,
for instance downloaded from the WildPackets website, then browse to the
folder where you unzipped the driver and select the net5211.inf file.
Otherwise, browse to the driver subdirectory in the directory where you installed the program and select the net5211.inf file
(for example C:\Program Files\WildPackets\OmniPeek\Driver\Atheros).
- Click on Open and then OK.
- Choose the appropriate manufacturer and network adapter (or "Atheros" if you don't see yours listed) and click on Next.
- Click on Yes to continue the installation if you receive a message saying
'Installing this driver is not recommended because Windows cannot verify that
it is compatible with your hardware.'.
- Click on 'Continue Anyway' to continue the installation if you receive a
message saying 'The software you are installing for this hardware: '...' has
not passed Windows Logo testing to verify its
compatibility with Windows XP.'.
- If asked for file "ar5211.sys", browse again to the directory in step 7 or
choose it from the popup list.
- Click on Finish to complete the installation and close the
properties window.
- Select Yes to reboot if asked. If not asked, we recommend that you reboot
the computer anyway.
IMPORTANT!
You must first install and test the adapter with the OEM driver. Do
not install the WildPackets driver until the adapter is functioning
properly on your network using the OEM driver.
IMPORTANT!
During our testing we have found that some OEM wireless configuration utilities for
Windows 2000 conflict with Peek. The symptom of the conflict is that the adapter
doesn't show up (at all) in the list of adapters displayed in Peek's adapter selection dialog.
If that happens, the workaround is to exit the OEM wireless configuration
utility if it is running, then remove it from the "Startup"
folder of the "Start" menu. You can do that by right-clicking on it and
selecting delete from the pull-down menu. You should reboot the computer after
removing the utility from the "Startup" folder to ensure that the utility is not
still running in the background.
Install the Peek product if it's not already installed.
To install the WildPackets driver, follow these steps:
- Go to Start Menu | Settings | Network and Dial-up Connections.
- Select the appropriate connection, right-click on it, and select
properties.
- Click on Configure, the Driver tab, and then on Update driver.
- Click on Next, 'Display a list of the known drivers for this
device...', and then on Next.
- Click the Have Disk button.
- If you received this driver independently from the program,
for instance downloaded from the WildPackets website, then browse to the
folder where you unzipped the driver and select the net5211.inf file.
Otherwise, browse to the driver subdirectory in the directory where you installed the program and select the net5211.inf file
(for example C:\Program Files\WildPackets\OmniPeek\Driver\Atheros).
- Click on Open and then OK.
- Choose the appropriate manufacturer and network adapter (or "Atheros" if you don't see yours listed) and click
on Next.
- Click on Yes to continue the installation if you receive a message saying
'Installing this driver is not recommended because Windows cannot verify that
it is compatible with your hardware.'.
- Click on Yes to continue the installation if you receive a
message saying 'Digital Signature was Not Found'.
- If asked for file "ar5211.sys", browse again to the directory in
step 6 or choose it from the popup list.
- Click on Finish to complete the installation and close the
properties window.
- Select Yes to reboot if asked. If not asked, we recommend that you reboot
the computer anyway.
WildPackets, Inc.
1340 Treat Blvd., Suite 500
Walnut Creek CA 94597 USA
(925) 937-3200
http://www.wildpackets.com/support/contact
Copyright © 2001-2006 WildPackets, Inc.
All rights reserved.