User Tools

Site Tools


compatibility_drivers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
compatibility_drivers [2013/11/24 04:35]
mister_x [PCMCIA/Cardbus/Express Card] Updated links and removed dead link/note
compatibility_drivers [2017/10/05 00:38] (current)
mister_x [Introduction] Fixed link to old page.
Line 1: Line 1:
-====== ​Introduction ​======+======= ​Determine the chipset and driver of a wireless card =======  
 + 
 +===== Introduction ​=====
  
 **IMPORTANT:​** **IMPORTANT:​**
   *Please read and understand the following prior to using this page: [[compatible_cards|Tutorial:​ Is My Wireless Card Compatible?​]]   *Please read and understand the following prior to using this page: [[compatible_cards|Tutorial:​ Is My Wireless Card Compatible?​]]
-  * Microsoft Windows ​and all variants are **NOT** officially ​supported ​at this point in time+  * Microsoft Windows ​is only supported ​by Airpcap for now. See [[install_drivers#​windows|this section]] for more details
-  * See this [[faq#​what_is_the_best_wireless_card_to_buy|FAQ entry]] if your question is "[[faq#​what_is_the_best_wireless_card_to_buy|What is the best wireless card to buy?]]". +  * See this [[faq#​what_is_the_best_wireless_card_to_buy|FAQ entry]] if your question is "What is the best wireless card to buy?".
  
 This section deals with a three related areas: This section deals with a three related areas:
  
-  *Compatibility ​of chipsets to the aircrack-ng suite +  * Determine the chipset ​of a wireless card 
-  *Which drivers are required ​for each type of chipset and operating system +  * Determine the driver ​for wireless ​card
-  *Which ​wireless ​cards are known to work with the aircrack-ng suite+
  
-====== Determine the chipset ====== +The previous version ​of this page can found [[compatibility_drivers_old|here]].
-There are two manufacturers involved with wireless cards. ​The first is the brand of the card itself. ​ Examples of card manufacturers are Netgear, Ubiquiti , Linksys and D-Link. There are many, many manufacturers beyond the examples give here.+
  
-The second manufacturer is who makes the wireless chipset within the card. This is the most important company to know.  Unfortunately,​ it is sometimes the hardest to determine. This is because card manufacturers generally don't want to reveal what they use inside their card. However, for our purposes, it is critical to know the wireless chipset manufacturer. Knowing the wireless chipset manufacturer allows you to determine which operating systems are supported, software drivers you need and what limitations are associated with them. The [[compatibility_drivers#​compatibility|compatibility]] ​section describes the operating systems supported and limitations by chipset.+===== Determine the chipset ===== 
 +There are two manufacturers involved with wireless cards. The first is the brand of the card itself. ​ Examples of card manufacturers are Netgear, Ubiquiti , Linksys, Interl and D-Link. There are many, many manufacturers beyond the examples give here. 
 + 
 +The second manufacturer is who makes the wireless chipset within the card. For example, Ralink, Atheros, Qualcomm. This is the most important company to know.  Unfortunately,​ it is sometimes the hardest to determine. This is because card manufacturers generally don't want to reveal what they use inside their card. However, for our purposes, it is critical to know the wireless chipset manufacturer. Knowing the wireless chipset manufacturer allows you to determine which operating systems are supported, software drivers you need and what limitations are associated with them. The next section describes the operating systems supported and limitations by chipset.
  
 You first need to determine what wireless chipset your card uses. This can be done by one or more of these techniques: You first need to determine what wireless chipset your card uses. This can be done by one or more of these techniques:
  
-  *Search the internet for "<​your card model> chipset"​ or "<​your card model> linux"​. Quite often you can find references to what chipset your card uses and/or other people'​s experiences. +  *Search the internet for "<​your card model> chipset"​ or "<​your card model> linux" ​or "<​your card model> wikidevi>​. Quite often you can find references to what chipset your card uses and/or other people'​s experiences. 
-  *Search the [[http://​forum.aircrack-ng.org/​|Forum]]+  *Search the [[https://​forum.aircrack-ng.org/​|Forum]]
   *You may also have a look at windows driver file names, it's often the name of the chipset or the driver to use.   *You may also have a look at windows driver file names, it's often the name of the chipset or the driver to use.
-  *Check later in this page for cards known to work with aircrack-ng 
   *Check the card manufacturers page. Sometimes they say what chipset they use.   *Check the card manufacturers page. Sometimes they say what chipset they use.
-  *Have a look at **lspci -vv** output for descriptions, ​PCI id and kernel modules used. +  *Have a look at **lsusb -vv** output for descriptions, ​USB id and kernel modules used. If the card is internal, do the same with **lspci -vv**
-  *Locate the [[http://​pictures.aircrack-ng.org/​fcc_id3.jpg|FCC ID]] of your device. Enter the information into [[http://transition.fcc.gov/​oet/​ea/​fccid/|FCC Website]] and then browse the internal photos of the device.+  *Locate the FCC ID of your device. Enter the information into [[https://www.fcc.gov/​oet/​ea/​fccid|FCC Website]] and then browse the internal photos of the device. ​Alternatively,​ use https://​fcc.io which is a shortcut. 
 + 
 +{{ http://​pictures.aircrack-ng.org/​fcc_id3.jpg }}
  
 \\ \\
 Here are some other resources to assist you in determine what chipset you have: Here are some other resources to assist you in determine what chipset you have:
  
-  * Linux-wireless has 3 pages depending on the device type: [[http://​wireless.kernel.org/​en/​users/​Devices/USB|USB]][[http://wireless.kernel.org/​en/​users/​Devices/​PCI|PCI/PCI Express/​MiniPCI/​MiniPCI Express/​Express Card/​Cardbus]] and the old [[http://wireless.kernel.org/en/users/​Devices/​PCMCIA|PCMCIA]] +  * Linux-wireless has [[https://wireless.wiki.kernel.org/​en/​users/​drivers|list of drivers in Linux]] 
-  * [[http://madwifi-project.org/wiki/Compatibility|Madwifi compatibility list]]+  * [[https://wikidevi.com|WikiDevi]] in general is a great resource for wireless ​devices/drivers/etc but if you are looking by device ID, check out [[https://wikidevi.com/wiki/List_of_Wi-Fi_Device_IDs_in_Linux|this page]].
   * [[http://​linux-wless.passys.nl/​|Wireless Adapter Chipset Directory]] nearly the best resource for this kind of information   * [[http://​linux-wless.passys.nl/​|Wireless Adapter Chipset Directory]] nearly the best resource for this kind of information
   * [[http://​atheros.rapla.net/​|Atheros chipsets based wireless 802.11a/b/g devices]] only Atheros-based cards   * [[http://​atheros.rapla.net/​|Atheros chipsets based wireless 802.11a/b/g devices]] only Atheros-based cards
-  * [[http://​www.seattlewireless.net/​index.cgi/​HardwareComparison|Hardware Comparison]] with a lot of details. 
-  * [[http://​s2p.de/​bin/​view/​Sysadmin/​ListeChipsatz|Overview]] and details about wireless adapters 
-  * [[http://​www.backtrack-linux.org/​wiki/​index.php/​Wireless_Drivers|BackTrack'​s old wiki]] outdated but may still contain relevant information 
-  * [[http://​acx100.sourceforge.net/​matrix.html|ACX1xx linux website]] 
-  ​ 
-\\ 
  
-^ Chipset ^ Supported by airodump for Windows ^ Supported by airodump for Linux ^ Supported by aireplay for Linux ^ 
-|Atheros|CardBus:​ YES\\ PCI: NO (see [[http://​www.tamos.com/​products/​commwifi/​adapterlist.php|CommView]])|PCI,​ PCI-E: YES\\ Cardbus/​PCMCIA/​Expresscard:​YES\\ USB: YES(b/g/n)| New mac80211 Atheros drivers have native injection and monitoring support| 
-|Atmel|UNTESTED|802.11b YES \\ 802.11g UNTESTED|UNTESTED| 
-|Broadcom bcm43xx|Old models only (BRCM driver)|YES|MOSTLY ([[http://​forum.aircrack-ng.org/​index.php?​topic=281.0|Forum thread]]) No fragmentation attack support. Recommend to use [[b43]], see below.| 
-|Broadcom b43|NO|Yes (1.0-beta2 and up, check [[b43|here]])|Yes,​ check [[b43|here]]| 
-|Centrino b|NO|PARTIAL\\ (ipw2100 driver doesn'​t discard corrupted packets)|NO| 
-|Centrino b/​g|NO|YES|NO (firmware drops most packets) [[ipw2200inject ]] No fragmentation attack support.| 
-|Centrino a/​b/​g|NO|YES|YES (use ipwraw or [[iwl3945]])| 
-|Centrino a/g/n (4965)|NO|YES|MOSTLY,​ see [[iwlagn]]. Fakeauth is currently broken.| 
-|Centrino a/g/n (5xxx)|NO|YES|YES| 
-|Cisco Aironet|YES?​|Yes,​ but very problematic|NO (firmware issue)| 
-|Hermes I|YES|Only with airodump not airodump-ng and only with a specific firmware|NO (firmware corrupts the MAC header)| 
-|NdisWrapper|N/​A|Never|Never| 
-|Prism2/​3|NO|old kernels only <​=2.6.20|YES (PCI and CardBus only: driver patching required) NOTE: Prism2/3 does not support shared key authentication and the fragmentation attack. ​ There is a [[http://​trac.aircrack-ng.org/​ticket/​288|critical bug]] and this chipset is not currently recommended. ​ It may even affect other kernel versions. Also you must use old kernel <​=2.6.20\\ USB: Only old kernel <=2.6.20 with linux-wlan-ng| 
-|PrismGT FullMAC|YES|YES|YES (driver patching recommended)| 
-|PrismGT SoftMAC|YES|YES (requires [[p54]] >​=2.6.30)|YES (requires [[p54]] >​=2.6.30)| 
-|Ralink|NO|YES|YES,​ see [[rt2x00]], [[rt2500]], [[rt2570]], [[rt61]] and [[rt73]]. ​ Also see Ralink chipset comments later on this pager for important concerns.| 
-|RTL8180|YES|YES|UNSTABLE (driver patching required)| 
-|RTL8185|NO|YES|YES (mac80211 driver untested)| 
-|RTL8187B/​RTL8197|NO|YES|YES (2.6.27+, use the [[mac80211]] driver with [[http://​patches.aircrack-ng.org/​rtl8187-mac80211-injection-speed-2.6.28-rc6.patch|this patch]])| 
-|RTL8187L|UNTESTED|YES (driver [[r8187|patching]] required to view power levels)|YES (driver [[r8187|patching]] recommended for injection and required to view power levels)| 
-|TI\\ (ACX100/​ACX111)|NO|YES|YES (driver [[acx|patching]] required) No fragmentation attack support. //Please re-test fragmentation with the [[acx1xx|mac80211 driver]] + mac80211 frag patch!//| 
-|ZyDAS 1201|NO|YES|Partially but NOT RECOMMENDED (See [[zd1211rw|patch]] for details)| 
-|ZyDAS 1211(B) softmac|NO|YES|Partially but NOT RECOMMENDED (See [[zd1211rw|patch]] for details). Atheros has acquired Zydas and renamed this chipset to AR5007UG.| 
-|ZyDAS 1211(B) mac80211|NO|YES ([[zd1211rw-mac80211|patching]] recommended)|YES,​ but no fragmentation attack support yet.| 
-|Other mac80211 (ADMtek...)|NO|UNTESTED,​ but likely YES|UNTESTED (YES for drivers with AP mode support)| 
-|Other legacy (Marvel...)|NO|UNKNOWN|NO| 
  
 ====== Determine the driver ====== ====== Determine the driver ======
 Once you have determined the chipset, check the [[compatibility_drivers#​drivers|driver]] section for which software driver you need. Software drivers connect the operating system to the hardware. The drivers are different for each operating system. There are also notes regarding limitations. Once you have determined the chipset, check the [[compatibility_drivers#​drivers|driver]] section for which software driver you need. Software drivers connect the operating system to the hardware. The drivers are different for each operating system. There are also notes regarding limitations.
  
-If you are deciding on which card to purchase, check the "[[compatibility_drivers#which_is_the_best_card_to_buy|Which is the best card to buy?​]]"​ section on this page. There are many considerations that should go into your purchase decision:+If you are deciding on which card to purchase, check the "[[faq#what_is_the_best_wireless_card_to_buy|What is the best wireless ​card to buy?​]]"​ section on this page. There are many considerations that should go into your purchase decision:
  
   *Hardware compatibility with your existing equipment.   *Hardware compatibility with your existing equipment.
Line 83: Line 53:
 It is not an easy decision to make. By considering these factors, it will help you make a more informed decision on what to purchase. It is not an easy decision to make. By considering these factors, it will help you make a more informed decision on what to purchase.
  
-\\ +====== ​Example: Alfa AWUS036AC ​======
- +
-^ Chipset ^ Windows driver (monitor mode) ^ Linux Drivers ^ Note ^ +
-|Atheros| [[http://​www.wildpackets.com/​support/​downloads/​driver_download/​1|v4.2]] or [[http://​www.wildpackets.com/​support/​downloads/​driver_download/​2|v3.0.1.12]] or [[http://​www.wildpackets.com/​support/​hardware/​atherosar5000_driver|AR5000]] \\ (see this [[http://​www.wildpackets.com/​support/​downloads/​drivers|page]] for more information)|[[http://​madwifi-project.org|Madwifi]],​ [[http://​wireless.kernel.org/​en/​users/​Drivers/​ath5k|ath5k]] [[http://​wireless.kernel.org/​en/​users/​Drivers/​ath9k|ath9k]],​ [[http://​linuxwireless.org/​en/​users/​Drivers/​ath9k_htc|ath9k_htc]] and [[http://​linuxwireless.org/​en/​users/​Drivers/​carl9170|ar9170/​carl9170]] |Atheros and Zydas USB 802.11n cards. The rest of atheros chipsets excluding the ones mentioned and MIMO series as well as fullMAC (these are rare, only found in embedded devices) should be supported.| +
-|Atheros| |[[http://​linuxwireless.org/​en/​users/​Drivers/​ath6kl|ath6kl]]|Third generation Atheros driver for mobile devices (AR6003)\\ Currently does not support ​ injection| +
-|Atmel| |[[http://​at76c503a.berlios.de|Atmel AT76c503a]]|AT76C503/​505A based USB WLAN adapters| +
-|Atmel| |[[http://​wireless.kernel.org/​en/​users/​Drivers/​at76_usb|Atmel AT76 USB]]|AT76C503/​505A based USB WLAN adapters, mac80211 driver| +
-|Broadcom|[[http://​www.wildpackets.com/​support/​hardware/​brcm_driver|Broadcom peek driver]]|[[http://​bcm43xx.berlios.de/​|bcm43xx]]|Windows:​ Old models only\\ Linux: always use latest -rc kernel| +
-|Broadcom with b43 driver| | [[http://​wireless.kernel.org/​en/​users/​Drivers/​b43|b43]] |[[b43|b43 - An excellent and fully supported driver]]| +
-|Broadcom 802.11n| | [[http://​wireless.kernel.org/​en/​users/​Drivers/​brcm80211|brcm80211]] |FOSS wireless driver for BCM4313, BCM43224, BCM43225 chipsets\\ Currently does not support monitor/​injection| +
-|Centrino b| |[[http://​ipw2100.sourceforge.net/​|ipw2100]]|802.11b only| +
-|Centrino b/g| |[[http://​ipw2200.sourceforge.net/​|ipw2200]]|See [[http://​www.kismetwireless.net/​blog/​index.php?​date=20060209|IPW2200 and RF-Mon]]. ​ See more recent [[http://​www.kismetwireless.net/​blog/​index.php?​date=20060308|update info here]] See this [[http://​forum.aircrack-ng.org/​index.php?​topic=1689.msg9343#​msg9343|thread]] for how to do injection.| +
-|Centrino a/b/g| | [[http://​ipw2200.sourceforge.net/​|ipw2915]]\\ [[http://​ipw3945.sourceforge.net/​|ipw3945]]\\ [[http://​wireless.kernel.org/​en/​users/​Drivers/​iwl3945|iwl3945]] |ipw2915 uses ipw2200 driver (See this [[http://​forum.aircrack-ng.org/​index.php?​topic=1387|thread]] for alpha injection support.) ​ For ipw3945 you can use the [[ipw3945]|ipwraw-ng driver]], [[iwl3945]|iwl3945 recommended on >=2.6.26]], or see [[links#​live_distributions|Live Distros]] for WifiWay which includes patches for injection.| +
-|Centrino a/g/n| | [[http://​intellinuxwireless.org/?​p=iwlwifi|iwlwifi]]| [[iwl4965|4965AGN under development]].| +
-|Cisco/​Aironet| [[http://​www.wildpackets.com/​support/​hardware/​ap_cisco_firmware|Cisco PCX500/​PCX504 peek driver]] | [[http://​airo-linux.sourceforge.net/​|airo-linux]] |4500/​4800/​340/​350 series, Firmware 4.25.30 recommended (see [[http://​www.wildpackets.com/​support/​hardware/​ap_cisco_firmware|this]] for more info)| +
-|Hermes I| [[http://​www.wildpackets.com/​support/​hardware/​ap_agere_driver|Agere peek driver]] | [[http://​www.hpl.hp.com/​personal/​Jean_Tourrilhes/​Linux/​Orinoco.html|Orinoco]]\\ [[http://​www.projectiwear.org/​~plasmahh/​orinoco.html|Orinoco Monitor Mode Patch]] |802.11b only and only with specific firmware (7.52)| +
-|Ndiswrapper|N/​A| [[http://​ndiswrapper.sourceforge.net/​|ndiswrapper]] |Using windows drivers in linux. It will **never** work with aircrack-ng| +
-|cx3110x \\ (Nokia 770/800)| |[[https://​garage.maemo.org/​projects/​cx3110x/​|cx3110x]]|Supports monitor mode (flaky) but not injection| +
-|prism2/​2.5|LinkFerret or aerosol| [[http://​hostap.epitest.fi/​|HostAP]]\\ [[http://​www.linux-wlan.com/​linux-wlan/​|wlan-ng]] |Use STA firmware >=1.5.6 (see [[Prism2_flashing|Prism2 flashing]])802.11b only, and only on old kernels <​=2.6.20. See this [[http://​forum.aircrack-ng.org/​index.php?​topic=3114.msg17446#​msg17446|forum entry]] regarding windows support.| +
-|prismGT| [[http://​500brabus.byethost22.com/​driver1.htm|PrismGT by 500brabus]] | [[http://​www.prism54.org/​|prism54]] |only FullMAC cards works with aircrack on Linux. Deprecated driver, refer to [[http://​linuxwireless.org/​en/​users/​Drivers/​p54|p54]].| +
-|prismGT (alternative) | | [[p54]] |mac80211 based, requires >=2.6.30 for better softMAC support. Also supports PrismGT FullMAC and PrismGT USB based chipsets.| +
-|Ralink| | [[http://​rt2x00.serialmonkey.com/​wiki/​index.php/​Main_Page|rt2x00]] or\\ [[http://​homepages.tu-darmstadt.de/​~p_larbig/​wlan/​|RaLink RT2570USB Enhanced Driver]] or\\ [[http://​homepages.tu-darmstadt.de/​~p_larbig/​wlan/​|RaLink RT73 USB Enhanced Driver]]|The entire rt2x00 family: rt2400pci, rt2500pci, rt2500usb, rt2800pci and rt2800usb can inject and monitor. Including PCI and USB chips on b/g/n.| +
-|Realtek 8180| [[http://​www.wildpackets.com/​support/​hardware/​ap_realtek_driver|Realtek peek driver]] | [[http://​rtl8180-sa2400.sourceforge.net/​|rtl8180-sa2400]] |802.11b only| +
-|Realtek 8187L| | [[r8187|r8187]]\\ [[rtl8187|rtl8187]]| | +
-|Realtek 8187B| | [[rtl8187]] (2.6.27+) or [[r8187b|r8187b (beta)]]| | +
-|TI|  | [[http://​acx100.sourceforge.net/​|ACX100/​ACX111/​ACX100USB]] | | +
-|ZyDAS 1201| | [[http://​linux-lc100020.sourceforge.net|zd1201]] |802.11b only| +
-|ZyDAS 1211| | [[http://​wireless.kernel.org/​en/​users/​Drivers/​zd1211rw|zd1211rw]] plus [[zd1211rw-mac80211|patch]] | Excellent USB chip with reliable aircrack-ng and general support | +
- +
-====== Which is the best card to buy ?  ====== +
-===== Atheros Chipset Comments ​ ===== +
- +
-One of the best chipsets nowadays is Atheros. It is very well supported under Linux, and also under Windows. The latest madwifi-ng patch makes it possible to inject raw 802.11 packets in either in Managed and Monitor mode at arbitrary b/g speeds. +
- +
-The [[http://​madwifi-project.org/​wiki/​Compatibility|madwifi-ng compatability list]] is an excellent way to determine if a card is compatible with the aircrack-ng suite. +
- +
-The madwifi-ng driver is used for the atheros chipsets. ​ This driver does not support any USB atheros devices. ​ However, Atheros acquired Zydas which makes USB chipsets (zd1211 and zd1211b). ​ Atheros has renamed this chipset to AR5007UG. ​ The AR5007UG chipset is NOT supported by the madwifi-ng driver, but it is recommended,​ because its one of the cheapest chips (about 5, 6$ on eBay) supported by aircrack-ng and offers reliable and stable operation for wireless connectivity. Starting with 2.6.24, AR5007UG(zd1211/​zd1211b) can be used with [[http://​forum.aircrack-ng.org/​index.php?​topic=5334.0|zd1211rw]]. Madwifi-ng is deprecated and now most supported cards by madwifi-ng should be supported by ath5k or ath9k. +
- +
-Another USB chipset, AR9170, which covers Atheros and Zydas chipsets (zd1221) also provides aircrack-ng support with a mac80211 driver called [[http://​wireless.kernel.org/​en/​users/​Drivers/​carl9170|carl9170]]. So does the [[http://​wireless.kernel.org/​en/​users/​Drivers/​ath9k_htc|ath9_htc]] for USB chips: AR9271 and AR7010. +
- +
- +
-As of kernel 2.6.26 and later, a new driver has been incorporated named as [[ath5k]]. This driver, unlike the madwifi-ng driver which requires HAL and was previously proprietary is a HAL-free based driver. Most popular linux distributions would already have this driver included which should provide support for those using such chipsets and preferrably to try injection patches on this driver before reverting back to the madwifi-ng. +
- +
-Also, with [[ath5k]] comes [[ath9k]], introduced for Atheros 802.11n capable chipsets. The [[ath5k]] and [[ath9k]] are not compatible as they have different designs. +
- +
-For more information refer to this [[http://​wireless.kernel.org/​en/​users/​Drivers/​Atheros|page]]. It contains updated information on upcoming support for other atheros chipsets (except for atheros MIMO). +
- +
-===== Broadcom Chipset Comments ===== +
- +
-Broadcom'​s "​AirForce One" line of chipsets is recently catching up with Atheros in terms of Linux support. The new [[b43]]/​b43legacy driver in 2.6.24 and up, when patched, can inject at speeds pretty much on par with Atheros. It also handles all attacks nicely, including fragmentation (although the underlying stack, [[mac80211]],​ requires a patch to inject fragments). Current development versions of the driver can actually reach speeds higher than those possible with Atheros, often up to 700 PPS and over. Multi-VAP operation/​concurrent monitor and managed interfaces, similar to the one seen in Madwifi, is also implemented through the underlying mac80211 stack. +
- +
-Windows, on the other hand, is not supported, except for some older 802.11b-only chipsets. +
- +
-Like Madwifi, b43 offers no support for Broadcom-based USB devices. For those, a separate driver called rndis_wlan exists, which doesn'​t support monitor mode (and will never do so, as the chipset has no raw mode). Draft-N devices are also not yet supported. +
- +
-Users whom use broadcom linux_sta driver (otherwise known as wl) should note that there are no monitor/​injection modes with such driver. Broadcom deliberately removed the functionality out of their proprietary binary blob. Read here for more info: http://​seclists.org/​fulldisclosure/​2008/​Nov/​506. Also b43 supports less than a handful of chipsets, take note on which ones are unsupported and see if yours fall into that category: [[b43]] +
- +
-===== Intel Chipset Comments ​  ​===== +
- +
-Intel wireless cards are common devices found inside most laptops apart from Broadcom, Atheros, Ralink and Realtek. These devices has native linux support and generally do work well for most parts except for Intel'​s older chipsets such as [[ipw2200]]. 3945 owners are recommended to use [[iwl3945]] as the older driver [[ipw3945]] does not have monitor or injection capability and requires [[ipw3945|ipwraw-ng]] and is often not easy to work with [[ipw3945|ipwraw-ng]]. Owners of 4965 and later has support with [[iwlagn]]. +
- +
-===== Intersil/​Conexant Chipset Comments ===== +
- +
-Intersil chipsets were well known back in the old days of wireless identification. The company had open designs and schematics for most of its products along with the source code (firmware remains proprietary but otherwise). These chipsets quickly gained the linux support due to the company'​s open handed approach until it was purchased by Conexant.  +
- +
-The legacy chipsets, namely Intersil Prism 2, Prism 2.5 and Prism 3 struggle in terms of support as the owners are slowly fading away. The drivers were split between the connecting interfaces on linux platform. Pre prismGT models had the [[hostap]] driver for most PCI/PCMCIA cards and [[wlan-ng]] for USB devices. These drivers are based on legacy stack and has two main drawbacks:​ +
- +
-1) They are buggy in which they would operate, for example [[wlan-ng]] does not obey iwconfig commands and requires its tool in order to change the modes, even to turn the device on so that iwconfig will start displaying information from the driver. +
- +
-2) The injection patches only work on older kernels, so for kernels beyond 2.6.20 will not inject properly. So if one were to continue using legacy chipsets, they must use older kernel, old drivers and firmware or they will not gain the extra features. +
- +
-As for Intersil/​Conexant PrismGT chipsets, the support for these on linux has been making a comeback. Initially the [[prism54]] driver is only able to support fullMAC cards, the support for softMAC cards were all over the place such as the use of islsm. As of kernel 2.6.26, a new driver [[p54]] has been incorporated with plans to merge both fullMAC and softMAC support of Intersil/​Conexant PrismGT product range. The initial code was buggy but users with >=2.6.28 kernel will benefit regardless of which PrismGT they own.  +
- +
-===== Ralink Chipset Comments ​ ===== +
- +
-Ralink makes some nice b/g chipsets, and has been very cooperative with the open-source community to release GPL drivers. Packet injection is now fully supported under Linux on PCI/CardBus RT2500 cards, and also works on USB RT2570 devices. ​ However, these cards are very temperamental,​ hard to get working, and have a tendency to work for a while then stop working for no reason. Furthermore,​ the RT2570 driver (such as that for the chipset inside the Linksys WUSB54Gv4) is currently unusable on big endian systems, such as the PowerPC. Cards with Ralink chipsets should not be your first choice. +
- +
-There is one exception with regards to the Ralink chipsets. ​ This is the [[rt73|RT73]] chipset. ​ There are excellent drivers with high injection rates for the [[rt73|RT73]] chipset. ​ Devices with the [[rt73|RT73]] chipsets are recommended. +
- +
-As of kernels >= 2.6.26 there are [[mac80211]] based drivers which should give better support for almost all Ralink chipsets. As for Ralink 802.11n capable devices, they are slowly gaining support, read [[rt2x00|here]]. +
- +
-===== Realtek RTL8187L Chipset Comments ​ ===== +
- +
-Cards containing the Realtek RTL8187L chipset work quite well and is recommended. ​ The driver patch for this chipset has been continuously improved and quite good at this point in time.  The Alfa AWUS036H is a very popular card with this chipset and it performs well the aircrack-ng suite. This chipset is not to be confused with the RTL8187B, which is nowhere near as tested as RTL8187L. +
- +
-===== List of compatible adapters ​ ===== +
-==== PCMCIA/​Cardbus/​Express Card==== +
- +
-^Card name^Type^Chipset^Antenna^Windows\\ support^Linux\\ support^Notes^ +
-|Airlink AWLC4030|CardBus|Atheros|Internal|airodump-ng|Yes| | +
-|Belkin F5D7010ED|Cardbus|Atheros|Internal|Not tested|Yes|[[http://​cache-www.belkin.com/​support/​dl/​p74217_f5d7010v1_man.pdf|Product manual]]| +
-|Belkin F5D8071|ExpressCard|Atheros|Internal|Not tested|Yes|[[http://​www.belkin.com/​IWCatProductPage.process?​Product_Id=439166|Product page]]| +
-|D-Link DWA-643|ExpressCard|Atheros|Internal|Unconfirmed\\ but likely|Yes|Draft N| +
-|D-Link DWL-650|PCMCIA|Prism 2.5|Internal|airodump-ng|Yes|See critical\\ chipset notes\\ above| +
-|D-Link DWL-G630 **C2 v3.01**|CardBus|Atheros|Internal|airodump-ng|Yes| | +
-|D-Link DWL-G630 **E1**|CardBus|Ralink|Internal|airodump-ng|Yes| | +
-|D-Link DWL-G650\\ **C3**, **C4**, **B5**|CardBus|Atheros|Internal or\\ [[http://​www.tutofr.com/​tutoriaux/​crack-wep/​tutorial-antenne-dwl-g650.php|RP-SMA]]|airodump-ng|Yes| | +
-|Linksys WPC55AG\\ **v1.2**|Cardbus|Atheros|Internal|Yes|Yes| | +
-|MSI CB54G2|CardBus|Ralink|Internal|No|Yes| | +
-|Netgear WAG511|CardBus|Atheros|Internal|airodump-ng|Yes| | +
-|Netgear WG511T|CardBus|Atheros|Internal|airodump-ng|Yes|See note 1| +
-|Netgear WG511U|CardBus|Atheros|Internal|airodump-ng|Yes| | +
-|Proxim 8470-WD|CardBus|Atheros|MC + Int.|airodump-ng|Yes| | +
-|Senao NL-2511\\ CD PLUS EXT|PCMCIA|Prism 2.5|MMCX|No|Yes|See critical\\ chipset notes\\ above| +
-|SMC SMCWCBT-G|Cardbus|Atheros|Internal|airodump-ng|Yes| | +
-|TP-Link TL-WN610G|Cardbus|Atheros|Internal|airodump-ng|Yes| | +
-|TrendNet TEW-441PC|Cardbus|Atheros|Internal|airodump-ng|Yes| | +
-|Ubiquiti SRC|CardBus|Atheros|MMCX|airodump-ng|Yes| | +
- +
-**Notes**:​ +
-  - There are some cheaper models with a similar name (WG511 and DWL-G520+); those cards are not Atheros-based. Also, the Peek driver does not support recent Atheros cards, so you'll have to use CommView WiFi instead. +
- +
-==== PCI/​MiniPCI/​MiniPCI Express==== +
- +
-^Card name^Type^Chipset^Antenna^Windows\\ support^Linux\\ support^Notes^ +
-|Airlive WT-2000PCI|PCI|RT61|RP-SMA|No|Yes| | +
-|ASUS WL-138G V2|PCI|Broadcom|RP-SMA|No|Yes|See Note 1 and 2| +
-|ASUS WL-138gE|PCI|Broadcom|RP-SMA|No|Yes|See Note 1 and 2| +
-|Broadcom BCM94311MCG|Mini-PCI Express|Broadcom|U.fl|No|Yes| | +
-|Compex WLM54G|Mini-PCI|Atheros|Internal|airodump-ng|Yes| | +
-|Canyon CN-WF511|PCI|Ralink RT61|RP-SMA|No|Yes| | +
-|D-Link DWL-G550|PCI|Atheros|RP-SMA|airodump-ng|Yes| | +
-|D-Link DWA-510|PCI|Ralink RT61|RP-SMA|No|Yes| | +
-|Linksys WMP54G **v4**|PCI|Ralink|RP-SMA|No|Yes| | +
-|Linksys WMP54G-UK **v4.1**|PCI|Ralink RT61|RP-SMA|No|Yes| | +
-|Linksys WMP110 RangePlus|PCI|Atheros|RP-SMA|No|Yes| | +
-|MSI PC54G2|PCI|Ralink|RP-SMA|No|Yes| | +
-|Netgear WG311T|PCI|Atheros|RP-SMA|airodump-ng|Yes|See Note 3| +
-|Netgear WPN311|PCI|Atheros|RP-SMA|airodump-ng|Yes| | +
-|Thinkpad 11a/​b/​g|Mini-PCI\\ Express|Atheros|U.fl|Unconfirmed\\ but likely|Yes|See Note 4| +
-|Ubiquiti SR71-E|PC Express|Atheros|MMCX|airodump-ng|Yes|Also SR71-E/X/C work| +
-|TP-Link TL-WN650G|PCI|Atheros|Soldered-in|airodump-ng|Yes|See Note 5| +
-|TP-Link TL-WN651G|PCI|Atheros|RP-SMA|airodump-ng|Yes| | +
-|Trendnet\\ TEW-443PI **A1 1R**|PCI|Atheros|RP-SMA|airodump-ng|Yes| | +
- +
-**Note**: +
-  - There is an earlier version of these cards called "​WL-138g",​ which is Marvell-based and thus unsupported. +
-  - 2.6.25.1 or newer kernel is required if you want to use this card with b43. +
-  - Netgear WG311 **v1** is likely compatible (Atheros). ​ Revision 2 is experimental (ACX chipset). Revision 3 (Marvell) is unsupported. ​ See http://​madwifi-project.org/​wiki/​Compatibility/​Netgear#​WG311. +
-  - See this [[http://​forum.aircrack-ng.org/​index.php?​topic=1387.msg8549#​msg8549|thread]] for important considerations. ​ See this [[http://​www5.pc.ibm.com/​uk/​products.nsf/​$wwwPartnumLookup/​_40Y7026?​OpenDocument|link]] for the card details. ​ Part number: 40Y7026. +
-  - This card has a soldered-in external antenna, with the wire between the card and the antenna easily pigtailable to RP-SMA. +
- +
- +
-==== USB ====+
  
-^Card name^Chipset^Antenna^Windows\\ support^Linux\\ support^Notes^ +Searching ​for "Alfa AWUS036AC wikidevi"​ returns me [[https://wikidevi.com/wiki/ALFA_Network_AWUS036AC|this page]] ​on WikiDevi.
-|Asus\\ WL-167g ** v2 **|Ralink RT73|Internal|No|Yes| | +
-|Airlink AWLL3026|Zydas zd1211|Internal|No|Yes|USB info: 0ace:1211 \\ See Notes 1 and 4.| +
-|Alfa AWUS036E|RTL8187L|RP-SMA|No|Yes|80mW| +
-|Alfa AWUS036H|RTL8187L|RP-SMA|No|Yes|[[http://​www.tuto-fr.com/​en/​tutorial/​materiel/​awus036h-alfa-network.php|Click here]] ​for a test of this adapter|  +
-|Alfa AWUS036S|Ralink rt73|RP-SMA|No|Yes|[[http://www.tuto-fr.com/en/tutorial/​materiel/​awus036s-alfa-network.php|Click here]] for a test of this adapter| +
-|Alfa AWUS050NH|Ralink RT2770F|RP-SMA|No|Yes| | +
-|Digitus DN-7003GS|RTL8187L|Internal|No|Yes|USB info: 0bda:8187 Realtek Semiconductor Corp. \\ [[http://​www.digitus.info/​scripts/​digdetail.asp?​artnr=DN%2D7003GS|Manufacturer ​page]]|  +
-|D-Link DWL-G122 **B1**|Ralink RT2570|Internal|No|Yes| | +
-|D-Link DWL-G122 **C1**|Ralink RT73|Internal|No|Yes| | +
-|D-Link WUA-1340|Ralink RT73|Internal|No|Yes| | +
-|Edimax EW-7318USg|Ralink rt73|RP-SMA|No|Yes|See\\ Note 2| +
-|Hawking HWUG1|Ralink rt73|RP-SMA|No|Yes| | +
-|Linksys WUSB54G **v4**|Ralink rt2570|Internal or\\ [[http://​www.egidy.de/​wifi/​wusb54g/​|RP-SMA]]|No|Yes| | +
-|Linksys WUSB54GC **v1**|Ralink RT73|Internal|No|Yes|See\\ Note 5 | +
-|Linksys WUSB54GC **v2**|RTL8187B|Internal|No|Yes|See\\ Note 5 | +
-|Netgear WG111 **v1**|PrismGT SoftMAC|Internal|airodump-ng|Untested|See note 3. Needs a recent GIT kernel from the wireless-testing branch.| +
-|Netgear WG111 **v2**|RTL8187L|Internal|No|Yes|See note 3| +
-|Netgear WG111 **v3**|RTL8187B|Internal|No|Yes|See note 3| +
-|Netgear WNDA3100 **v1**|Atheros 9170|Internal|No|Yes|See Note 6| +
-|TP-Link\\ TL-WN321G|Ralink RT73|Internal|No|Yes|[[http://​www.tp-link.com/​products/​product_des.asp?​id=47|Manufacturer page]]| +
-|TP-Link\\ TL-WN321G **v4**|Ralink RT2070|Internal|No|Yes|Supported by rt2800usb| +
-|Trendnet\\ TEW-429UB **C1**|Zydas zd1211b|Internal|No|Yes|USB info: 157e:300d \\  | +
-|ZyXEL AG-225H|Zydas zd1211|Internal|No|Limited|See Note 4| +
-|ZyXEL G-202|Zydas zd1211b|Internal|No|Limited|See Note 4|+
  
 +{{ :​awus036ac_wikidevi_1.png?​200|}}
 +The box on the right contain all the information needed to identify the chipset manufacturer and model. In this case, RTL8812AU.
  
-**Notes**:+It also lists the IDs (**0bda:8812**) which is what would be returned on Linux with the //lsusb// command, right next to **ID**.
  
-  - See this [[http://​forum.aircrack-ng.org/​index.php?​topic=2862.msg17501#​msg17501|thread message]] comments ​on this device+If it were on Windows, even if the drivers were not installed, looking in the device ​managerthat ID would be found in Details pane of the device itself, in the property "​Hardware IDs"This is also displayed in WikiDevi: **USB\VID_0BDA&​PID_8812** (this is the same as the IDs on Linuxthey'​re just uppercase and they contain some text around: USB device, VID stands for Vendor ID, PID stands for product ID).
-  - See this [[http://​forum.aircrack-ng.org/​index.php?​topic=1731.0|thread]] for pictureslinks and other information. +
-  - Netgear WG111: This [[http://​kbserver.netgear.com/​products/​wg111.asp|Netgear support page]] describes which serial numbers are for each version ​of the card. +
-  - See [[zd1211rw]] for the limitations. +
-  - WUSB54GC v1 is silver-colored,​ v2 is whitev3 is black. +
-  - V2 isn't supported yet (only by wl but wl doesn'​t support monitor mode+
  
-===== Zaurus Compatible Card ====+{{:​awus036ac_wikidevi_2.png?​200 |}}
  
-All prism2 ​or prism2.5 on this [[http://​www.oesf.org/​index.php?​title=Wireless_Card_Support|wireless card support page]] can inject.+Searching for that ID in WikiDevi ​or any search engine would also help finding the chipset and driver requiredMultiple pages would be returned because multiple adapters share the same USB ID.
  
-====== ExpressCard ​to PCMCIA/​Cardbus Adapters ======+The exact same principles apply to internal devices, the only difference is they will be found under **lspci**.
  
-New laptops now normally come with ExpressCard slots The current problem ​is that there are not a lot of ExpressCard wireless cards which are compatible with the aircrack-ng suite. ​ However, ExpressCard ​to PCMCIA/​Cardbus adapters have appeared ​in the market.+Another way to find the chipset/​driver,​ after exhausting the options above, if you don't have the device itself is to download the driverIt is very useful when searching for laptops ​that are too new to be in any search engine results.
  
-The question has always been "Will these adapters work correctly with the aircrack-ng suite"Read this [[http://​forum.aircrack-ng.org/​index.php?​topic=2849|thread]] ​and this [[http://​forum.aircrack-ng.org/​index.php?​topic=6864.0|thread]] for the details.+In this case, the Windows driver of the AWUS036ACIt doesn'​t really matter which version of Windows, the important information are some filenames (and content).
  
-If you try any adapters, please post your findings (good or bad) to the forum. ​ This is very important so that everyone can benefit from the experiences of others.+{{ :​awus036ac_inf_file.png?200|}}
  
-Here is list of adapters ​that people ​have reported as working successfully:​+Sometimes the name of the files (//.cat//, //.inf// and //.sys//) can indicate the chipset codename. Most of the time, they don't and the .inf file needs to be opened in text editor (supporting UTF-16). Scroll down and there will be lists of IDs that are supported by that driver. In this example, the driver supports both PCI and USB Realtek devices, so, it will help narrow down what compatibility you have to look for on Linux.
  
-  * [[http://addonics.com/products/host_controller/adexc34cb.asp|Addonics ADEXC34CB]] ExpressCard 34 Cardbus Adapter +If the driver is packed in an executable (//.msi// or //.exe//), unpacking will be requiredSometimes multiple times, such as when it is bundled with a WiFi managerUniExtract (Universal Extractor) is one of the tools to do so.
-  * [[http://www.rosewill.com/products/s_1227/​productDetail.htm|Rosewill RC-608]] ​ ExpressCard to CardBus Adapter. ​ It can be purchased [[http://​www.newegg.com/​Product/​Product.aspx?​Item=N82E16839200010&​cm_re=rc-608-_-39-200-010-_-Product|here]].+
compatibility_drivers.1385264117.txt.gz · Last modified: 2013/11/24 04:35 by mister_x