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 [2017/01/10 23:47]
mister_x Overhaul - Work in Progress
compatibility_drivers [2017/10/05 00:38] (current)
mister_x [Introduction] Fixed link to old page.
Line 1: Line 1:
-======= Determine the chipset of a wireless card ======= ​+======= Determine the chipset ​and driver ​of a wireless card ======= ​
  
 ===== Introduction ===== ===== Introduction =====
Line 5: Line 5:
 **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 "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:
Line 13: Line 12:
   * Determine the chipset of a wireless card   * Determine the chipset of a wireless card
   * Determine the driver for a wireless card   * Determine the driver for a wireless card
 +
 +The previous version of this page can found [[compatibility_drivers_old|here]].
  
 ===== Determine the 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 and D-Link. There are many, many manufacturers beyond the examples give 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, 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. 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.+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 [[https://​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 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 **lsusb -vv** output for descriptions,​ USB id and kernel modules used. If the card is internal, do the same with **lspci -vv**.   *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 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 }} {{ http://​pictures.aircrack-ng.org/​fcc_id3.jpg }}
  
Line 36: Line 38:
   * [[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://​s2p.de/​bin/​view/​Sysadmin/​ListeChipsatz|Overview]] and details about wireless adapters 
-  ​ 
-\\ 
  
-^ 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 81: 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 ====== 
 + 
 +Searching for "Alfa AWUS036AC wikidevi"​ returns me [[https://​wikidevi.com/​wiki/​ALFA_Network_AWUS036AC|this page]] on WikiDevi. 
 + 
 +{{ :​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. 
 + 
 +It also lists the IDs (**0bda:​8812**) which is what would be returned on Linux with the //lsusb// command, right next to **ID**. 
 + 
 +If it were on Windows, even if the drivers were not installed, looking in the device manager, that 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 Linux, they'​re just uppercase and they contain some text around: USB device, VID stands for Vendor ID, PID stands for product ID). 
 + 
 +{{:​awus036ac_wikidevi_2.png?​200 |}} 
 + 
 +Searching for that ID in WikiDevi or any search engine would also help finding the chipset and driver required. Multiple pages would be returned because multiple adapters share the same USB ID. 
 + 
 +The exact same principles apply to internal devices, the only difference is they will be found under **lspci**. 
 + 
 +Another way to find the chipset/​driver,​ after exhausting the options above, if you don't have the device itself is to download the driver. It is very useful when searching for laptops that are too new to be in any search engine results. 
 + 
 +In this case, the Windows driver of the AWUS036AC. It doesn'​t really matter which version of Windows, the important information are some filenames (and content). 
 + 
 +{{ :​awus036ac_inf_file.png?​200|}} 
 + 
 +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 a 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.
  
-^ Chipset ^ Windows ​driver (monitor mode) ^ Linux Drivers ^ Note ^ +If the driver ​is packed in an executable ​(//.msi// or //.exe//), unpacking will be requiredSometimes multiple timessuch as when it is bundled ​with a WiFi managerUniExtract ​(Universal Extractoris one of the tools to do so.
-|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 |+
compatibility_drivers.1484088426.txt.gz · Last modified: 2017/01/10 23:47 by mister_x