compatibility_drivers
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
compatibility_drivers [2010/11/18 14:54] – [Determine the driver] - reshuffle & add some drivers sleek | compatibility_drivers [2018/07/20 23:16] – Updated determine driver mister_x | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ======= |
+ | |||
+ | ===== Introduction | ||
**IMPORTANT: | **IMPORTANT: | ||
*Please read and understand the following prior to using this page: [[compatible_cards|Tutorial: | *Please read and understand the following prior to using this page: [[compatible_cards|Tutorial: | ||
- | * Microsoft Windows | + | * Microsoft Windows |
- | * See this [[faq# | + | * See this [[faq# |
+ | This section deals with two related areas: | ||
- | This section deals with a three related areas: | + | * Determine the chipset of a wireless card |
+ | * Determine the driver for a wireless card | ||
- | *Compatibility | + | The previous version |
- | *Which drivers are required for each type of chipset and operating system | + | |
- | *Which wireless cards are known to work with the aircrack-ng suite | + | |
- | ====== Determine the chipset | + | ===== Determine the chipset ===== |
- | There are two manufacturers involved with wireless cards. The first is the brand of the card itself. | + | There are two manufacturers involved with wireless cards. The first is the brand of the card itself. |
- | The second manufacturer is who makes the wireless chipset within the card. This is the most important company to know. Unfortunately, | + | 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, |
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 "< | + | *Search the internet for "< |
- | *Search the [[http:// | + | *Search the [[https:// |
*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, | + | *Have a look at **lsusb -vv** output for descriptions, |
- | *Locate the [[http:// | + | *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. |
+ | |||
+ | {{ http:// | ||
\\ | \\ | ||
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: | ||
- | * [[http://madwifi-project.org/wiki/Compatibility|Madwifi compatibility | + | * Linux-wireless has a [[https://wireless.wiki.kernel.org/en/users/ |
+ | * [[https:// | ||
* [[http:// | * [[http:// | ||
* [[http:// | * [[http:// | ||
- | * [[http:// | ||
- | * [[http:// | ||
- | * [[http:// | ||
- | * [[http:// | ||
- | * [[http:// | ||
- | * [[http:// | ||
- | | ||
- | \\ | ||
- | ^ Chipset ^ Supported by airodump for Windows ^ Supported by airodump for Linux ^ Supported by aireplay for Linux ^ | ||
- | |Atheros|CardBus: | ||
- | |Atmel|UNTESTED|802.11b YES \\ 802.11g UNTESTED|UNTESTED| | ||
- | |Broadcom bcm43xx|Old models only (BRCM driver)|YES|MOSTLY ([[http:// | ||
- | |Broadcom b43|NO|Yes (1.0-beta2 and up, check [[b43|here]])|Yes, | ||
- | |Centrino b|NO|PARTIAL\\ (ipw2100 driver doesn' | ||
- | |Centrino b/ | ||
- | |Centrino a/ | ||
- | |Centrino a/g/n (4965)|NO|YES|MOSTLY, | ||
- | |Centrino a/g/n (5xxx)|NO|YES|YES| | ||
- | |Cisco Aironet|YES? | ||
- | |Hermes I|YES|Only with airodump not airodump-ng and only with a specific firmware|NO (firmware corrupts the MAC header)| | ||
- | |NdisWrapper|N/ | ||
- | |Prism2/ | ||
- | |PrismGT FullMAC|YES|YES|YES (driver patching recommended)| | ||
- | |PrismGT SoftMAC|YES|YES (requires [[p54]] > | ||
- | |Ralink|NO|YES|YES, | ||
- | |RTL8180|YES|YES|UNSTABLE (driver patching required)| | ||
- | |RTL8185|NO|YES|YES (mac80211 driver untested)| | ||
- | |RTL8187B/ | ||
- | |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/ | ||
- | |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, | ||
- | |Other mac80211 (ADMtek...)|NO|UNTESTED, | ||
- | |Other legacy (Marvel...)|NO|UNKNOWN|NO| | ||
====== Determine the driver ====== | ====== Determine the driver ====== | ||
- | Once you have determined the chipset, check the [[compatibility_drivers# | ||
- | 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? | + | Once you have determined the chipset, chances are you already have identified the driver on Linux. If not, match the chipset against the "other resources" |
+ | |||
+ | On Linux, there can be multiple drivers: | ||
+ | - Vendor driver: those do not and will not support monitor mode | ||
+ | - Peer-modified vendor driver: In some cases, they may support monitor mode but there could be caveats | ||
+ | - Staging driver: Standalone driver has been added to the [[http:// | ||
+ | - Kernel/ | ||
+ | |||
+ | 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 | ||
*Hardware compatibility with your existing equipment. | *Hardware compatibility with your existing equipment. | ||
Line 84: | Line 60: | ||
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. | ||
- | \\ | + | ====== |
- | + | ||
- | ^ Chipset ^ Windows driver (monitor mode) ^ Linux Drivers ^ Note ^ | + | |
- | |Atheros| [[http:// | + | |
- | |Atheros| |[[http:// | + | |
- | |Atmel| |[[http:// | + | |
- | |Atmel| |[[http:// | + | |
- | |Broadcom|[[http:// | + | |
- | |Broadcom with b43 driver| | [[http:// | + | |
- | |Broadcom 802.11n| | [[http:// | + | |
- | |Centrino b| |[[http:// | + | |
- | |Centrino b/g| |[[http:// | + | |
- | |Centrino a/b/g| | [[http:// | + | |
- | |Centrino a/g/n| | [[http:// | + | |
- | |Cisco/ | + | |
- | |Hermes I| [[http:// | + | |
- | |Ndiswrapper|N/ | + | |
- | |cx3110x \\ (Nokia 770/800)| |[[https:// | + | |
- | |prism2/ | + | |
- | |prismGT| [[http:// | + | |
- | |prismGT (alternative) | | [[p54]] |mac80211 based, requires >=2.6.30 for better softMAC support. Also supports PrismGT FullMAC and PrismGT USB based chipsets.| | + | |
- | |Ralink| | [[http:// | + | |
- | |Realtek 8180| [[http:// | + | |
- | |Realtek 8187L| | [[r8187|r8187]]\\ [[rtl8187|rtl8187]]| | | + | |
- | |Realtek 8187B| | [[rtl8187]] (2.6.27+) or [[r8187b|r8187b (beta)]]| | | + | |
- | |TI| | [[http:// | + | |
- | |ZyDAS 1201| | [[http:// | + | |
- | |ZyDAS 1211| | [[http:// | + | |
- | + | ||
- | ====== 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:// | + | |
- | + | ||
- | The madwifi-ng driver is used for the atheros chipsets. | + | |
- | + | ||
- | Another USB chipset, AR9170, which covers Atheros and Zydas chipsets (zd1221) also provides aircrack-ng support with a mac80211 driver called [[http:// | + | |
- | + | ||
- | + | ||
- | 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:// | + | |
- | + | ||
- | ===== Broadcom Chipset Comments ===== | + | |
- | + | ||
- | Broadcom' | + | |
- | + | ||
- | 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' | + | |
- | + | ||
- | Users whom use broadcom linux_sta driver (otherwise known as wl) should note that there are no monitor/ | + | |
- | + | ||
- | ===== 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' | + | |
- | + | ||
- | ===== Intersil/ | + | |
- | + | ||
- | 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' | + | |
- | + | ||
- | 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/ | + | |
- | + | ||
- | ===== 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. | + | |
- | + | ||
- | There is one exception with regards to the Ralink chipsets. | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | ===== List of compatible adapters | + | |
- | ==== PCMCIA/ | + | |
- | + | ||
- | ^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:// | + | |
- | |Belkin F5D8071|ExpressCard|Atheros|Internal|Not tested|Yes|[[http:// | + | |
- | |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:// | + | |
- | |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 2| | + | |
- | |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**: | + | |
- | - See this link [[http:// | + | |
- | - 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/ | + | |
- | + | ||
- | ^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/ | + | |
- | |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 " | + | |
- | - 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). | + | |
- | - See this [[http:// | + | |
- | - 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 |
- | |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:// | + | |
- | |Alfa AWUS036S|Ralink rt73|RP-SMA|No|Yes|[[http://www.tuto-fr.com/en/tutorial/ | + | |
- | |Alfa AWUS050NH|Ralink RT2770F|RP-SMA|No|Yes| | | + | |
- | |Digitus DN-7003GS|RTL8187L|Internal|No|Yes|USB info: 0bda:8187 Realtek Semiconductor Corp. \\ [[http:// | + | |
- | |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:// | + | |
- | |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 WNDA3100 **v1**|Atheros 9170|Internal|No|Yes|See Note 6| | + | |
- | |TP-Link\\ TL-WN321G|Ralink RT73|Internal|No|Yes|[[http:// | + | |
- | |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| | + | |
+ | {{ : | ||
+ | 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:// | + | If it were on Windows, even if the drivers were not installed, looking in the device |
- | - See this [[http:// | + | |
- | - Netgear WG111: This [[http:// | + | |
- | - See [[zd1211rw]] for the limitations. | + | |
- | - WUSB54GC v1 is silver-colored, | + | |
- | - V2 isn't supported yet (only by wl but wl doesn' | + | |
- | ===== Zaurus Compatible Card ==== | + | {{: |
- | All prism2 | + | Searching for that ID in WikiDevi |
- | ====== ExpressCard | + | 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 | + | Another way to find the chipset/ |
- | The question has always been "Will these adapters work correctly with the aircrack-ng suite". Read this [[http:// | + | In this case, the Windows driver of the AWUS036AC. It doesn' |
- | If you try any adapters, please post your findings (good or bad) to the forum. | + | {{ : |
- | Here is a list of adapters | + | 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. |
- | * [[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 required. Sometimes multiple times, such as when it is bundled with a WiFi manager. UniExtract (Universal Extractor) is one of the tools to do so. |
- | * [[http://www.rosewill.com/products/s_1227/ | + |
compatibility_drivers.txt · Last modified: 2018/07/20 23:16 by mister_x