![Aircrack-ng Injection Driver Aircrack-ng Injection Driver](/uploads/1/2/6/3/126313257/263133908.png)
This is how you can get the Intel WiFi Link 4965AGN/5xxxAGN card to inject under Linux using the iwlwifi drivers. Please note that the injection is still under development, but is possible at this point. When monitor mode is set, injection is not working anymore. Device - driver - AFNETLINK - libnl - iw - airmon-ng = AFNETLINK.
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 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:
- 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.
- 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.
- Have a look at lspci -vv output for descriptions, PCI id and kernel modules used.
- Locate the FCC ID of your device. Enter the information into FCC Website and then browse the internal photos of the device.
Here are some other resources to assist you in determine what chipset you have:
- Linux-wireless has 3 pages depending on the device type: USB, PCI/PCI Express/MiniPCI/MiniPCI Express/Express Card/Cardbus and the old PCMCIA
- Wireless Adapter Chipset Directory nearly the best resource for this kind of information
- Atheros chipsets based wireless 802.11a/b/g devices only Atheros-based cards
- 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 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 (Forum thread) No fragmentation attack support. Recommend to use b43, see below. |
Broadcom b43 | NO | Yes (1.0-beta2 and up, check here) | Yes, check 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 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 this patch) |
RTL8187L | UNTESTED | YES (driver patching required to view power levels) | YES (driver patching recommended for injection and required to view power levels) |
TI (ACX100/ACX111) | NO | YES | YES (driver patching required) No fragmentation attack support. Please re-test fragmentation with the mac80211 driver + mac80211 frag patch! |
ZyDAS 1201 | NO | YES | Partially but NOT RECOMMENDED (See patch for details) |
ZyDAS 1211(B) softmac | NO | YES | Partially but NOT RECOMMENDED (See patch for details). Atheros has acquired Zydas and renamed this chipset to AR5007UG. |
ZyDAS 1211(B) mac80211 | NO | YES (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 |