Technical Notes on Hardware Compatibility

• Supported only under Windows Vista, Windows 7, Windows 8, Server 2008, and Server 2012 (except Intel 4965 that is NOT supported under Windows 8 or Server 2012).
• A compatible Intel driver version is required. Click here for more information.
• When install/updating the driver for your Intel adapter, install the driver only. Do not install "Intel PROSet/Wireless" or "Intel My WiFi" utilities; let Windows manage your Wi-Fi connection. If these utilities are installed, the application might be unable to capture packets.
• Packet injection using Packet Generator is not possible.
• Noise level is unavailable.
• When monitoring 802.11n networks, you cannot capture packets sent using 40 MHz channel bonding. This is an issue with the adapter driver that is out of our control.
• When monitoring 802.11n networks, the adapter driver reports the packet transmission rate of 802.11n packets incorrectly. For example, a packet with a rate of 130 Mbps might appear with a rate of 1 Mbps or 9 Mbps. This is an issue with the adapter driver that is out of our control.

• Supported only under Windows Vista, Windows 7, Windows 8, Server 2008, and Server 2012.
• Make sure that the Broadcom driver that you are using for your adapter is version 5 or higher. Older driver versions might not work properly in monitor mode.
• Packet injection using Packet Generator is not possible.
• Noise level is unavailable.
• When monitoring 802.11n networks, you cannot capture packets sent using 40 MHz channel bonding. This is an issue with the adapter driver that is out of our control.
• When monitoring 802.11n networks, the adapter driver reports the packet transmission rate of 802.11n packets incorrectly. For example, a packet with a rate of 130 Mbps might appear with a rate of 1 Mbps or 9 Mbps. This is an issue with the adapter driver that is out of our control.

• Supported only under Windows Vista, Windows 7, Windows 8, Server 2008, and Server 2012.
• Make sure that the Dell driver that you are using for your adapter is version 5 or higher. Older driver versions might not work properly in monitor mode. If you're using an older driver version, please visit http://support.dell.com/ to download the latest version. For Dell 1390, 1395, 1397, 1505, 1510, you may want to use this direct link to the driver download page.
• Packet injection using Packet Generator is not possible.
• Noise level is unavailable.
• When monitoring 802.11n networks, you cannot capture packets sent using 40 MHz channel bonding. This is an issue with the adapter driver that is out of our control.
• When monitoring 802.11n networks, the adapter driver reports the packet transmission rate of 802.11n packets incorrectly. For example, a packet with a rate of 130 Mbps might appear with a rate of 1 Mbps or 9 Mbps. This is an issue with the adapter driver that is out of our control.

• These adapters require Windows 7 or higher.
• The supported channel set in the 5 GHz band is limited. At the time of writing, Buffalo AC866 and NETGEAR A6200 support only the following 5 GHz channels: 36, 40, 44, 48, 149, 153, 157, 161, and 165. D-Link DWA-182 supports only the following 5 GHz channels: 36, 40, 44, and 48. The supported channel sets depend on the regulatory domain; the sets listed above are found in the adapters being sold in North America. The sets of the adapters being sold in other parts of the world might be different.
• Packet injection using Packet Generator is not possible.
• Noise level is unavailable.
• When monitoring 802.11n networks, you cannot capture packets sent using 40 MHz channel bonding. This is an issue with the adapter driver that is out of our control.
• When monitoring 802.11n networks, the adapter driver reports the packet transmission rate of 802.11n packets incorrectly. For example, a packet with a rate of 130 Mbps might appear with a rate of 1 Mbps or 9 Mbps. This is an issue with the adapter driver that is out of our control.

• The adapter drivers report an incorrect signal level (the same level for all packets) and incorrect data rate. They also don't indicate usable FCS values, which makes it impossible to distinguish between damaged and undamaged packets. These bugs make these adapters unusable for any serious network monitoring and analysis. If you want them fixed, please contact the driver manufacturer (and yes, Ralink will ignore you).
• Supported only under Windows Vista, Windows 7, Windows 8, Server 2008, and Server 2012.
• Packet injection using Packet Generator is not possible.
• Noise level is unavailable.
• When monitoring 802.11n networks, you cannot capture packets sent using 40 MHz channel bonding. This is an issue with the adapter driver that is out of our control.

• Supported only under Windows Vista, Windows 7, Windows 8, Server 2008, and Server 2012.
• Your driver version must be 2.2.0.11 or higher.
• Packet injection using Packet Generator is not possible.
• Noise level is unavailable.
• The adapter might sometimes fail to switch to a new channel when using the scanner.
• We do not recommend using this adapter for any serious monitoring purposes.

There are several hardware versions of this card: A1, B1/B2/B3/B4/B5, and C1/C2/C3/C4. CommView for WiFi DOES NOT support version A1. It DOES support versions B1/B2/B3/B4/B5 and C1/C2/C3/C4. To identify your card, please visit the D-Link site.

There are two hardware versions of this card: v1 and v2. To identify your adapter, look at the side of your adapter. If you see "WN111", then it's v1. If you see "WN111v2", then it's v2. CommView for WiFi DOES NOT support version v1. It DOES support version v2.

The notes below are applicable only to the version 2 of this adapter. Version 1 has no limitations. To check what version you have, look at the side of the adapter. If you have version 2, it is explicitly mentioned on one of the two side labels.

• Supported only under Windows Vista, Windows 7, Windows 8, Server 2008, and Server 2012.
• Make sure that the driver that you are using for your adapter is version 5.60.180.11 or higher. Older driver versions might not work properly in monitor mode.
• It is recommended that you install the driver for the adapter by using the automatic Windows update feature, i.e. by simply plugging in the adapter and allowing Windows to find the driver for it. This will install the driver without the "NETGEAR Smart Wizard" utility. If you install the driver from the CD-ROM provided by NETGEAR, the "NETGEAR Smart Wizard" utility will be installed. In this case, right-click on the "NETGEAR Smart Wizard" icon and uncheck the "Enable NETGEAR Smart Wizard" box, which ensures that the adapter is managed by Windows rather than the "NETGEAR Smart Wizard" utility. If the adapter is managed by the utility, you WILL NOT be able to use this adapter.
• Packet injection using Packet Generator is not possible.
• Noise level is unavailable.
• When monitoring 802.11n networks, you cannot capture packets sent using 40 MHz channel bonding. This is an issue with the adapter driver that is out of our control.
• When monitoring 802.11n networks, the adapter driver reports the packet transmission rate of 802.11n packets incorrectly. For example, a packet with a rate of 130 Mbps might appear with a rate of 1 Mbps or 9 Mbps. This is an issue with the adapter driver that is out of our control.

No custom driver installation is needed when using these adapters; use the driver supplied by the vendor. The AirPcap driver that you use must be version 4.0 or higher. This adapter cannot be used in dual (monitoring + connectivity) mode; it is a monitoring-only adapter.

• Supported only under Windows 7 or higher.
• Packet injection using Packet Generator is limited to only one send rate, 1 Mbps.
• Packet injection using Packet Generator may generate duplicate packets.
• TP-Link WN721N and WN722N are single-stream 802.11n cards; they cannot be used to capture packets from dual-stream (300 Mbps) 802.11n hardware.