| 1 |
Documentation, tutorials, ... can be found on https://www.aircrack-ng.org |
| 2 |
See also manpages and the forum (GitHub Discussions). |
| 3 |
|
| 4 |
Installing |
| 5 |
========== |
| 6 |
|
| 7 |
This version has more dependencies/libraries required than previous versions to be compiled. |
| 8 |
See INSTALLING file for more information |
| 9 |
|
| 10 |
OpenWrt Devices |
| 11 |
=============== |
| 12 |
|
| 13 |
You can use airodump-ng on OpenWrt devices. You'll have to use specify |
| 14 |
prism0 as interface. Airodump-ng will automatically create it. |
| 15 |
Rq: Aireplay DOESN'T work on OpenWrt (2.4 kernel) with broadcom chipset since the driver doesn't support injection. It *may* work with 2.6 kernels >= 2.6.24 (kamikaze 8.09+ custom-built). |
| 16 |
|
| 17 |
|
| 18 |
Known bugs: |
| 19 |
=========== |
| 20 |
|
| 21 |
Drivers |
| 22 |
------- |
| 23 |
|
| 24 |
Madwifi-ng |
| 25 |
---------- |
| 26 |
|
| 27 |
The cause of most of these problems (1, 2 and 3) is that Madwifi-ng cannot easily change the rate in monitor mode. |
| 28 |
Technically, when changing rate while in monitor mode, the raw socket gets invalidated and we have to get it again. |
| 29 |
Madwifi-ng is getting replaced by several drivers: ath5k, ath9k and ar9170. |
| 30 |
|
| 31 |
|
| 32 |
Problem 1: No client can associate to an airbase soft AP. |
| 33 |
Solution: Use a more recent driver. Madwifi-ng has been deprecated for years. |
| 34 |
|
| 35 |
|
| 36 |
Problem 2: When changing rate while you are capturing packet makes airodump-ng stall |
| 37 |
Solution 2: Restart airodump-ng or change rate before starting it. |
| 38 |
|
| 39 |
Problem 3: After some time it stops capturing packets and you're really sure no network manager are running at all. |
| 40 |
Solution 3: That's a known bug in the driver, it may happen at any time (the time before it fails can vary a lot: |
| 41 |
from 5 minutes to 50 or even more). Try (as root) unloading completely the driver with 'madwifi-unload' |
| 42 |
and then run 'modprobe ath_pci autocreate=monitor'. |
| 43 |
|
| 44 |
|
| 45 |
Problem 4: When creating a new VAP airodump-ng takes up to 10-15 seconds to see the first packet |
| 46 |
Solution 4: It's the behavior of madwifi-ng, don't worry (... be happy ;)). |
| 47 |
|
| 48 |
|
| 49 |
Orinoco |
| 50 |
------- |
| 51 |
|
| 52 |
Problem: BSSID is not reported correctly or is 00:00:00:00:00:00 or signal is not reported correctly. |
| 53 |
Solution: None. Consider replacing your card, orinoco is really really old. |
| 54 |
|
| 55 |
|
| 56 |
Aircrack-ng |
| 57 |
----------- |
| 58 |
|
| 59 |
Aireplay-ng |
| 60 |
----------- |
| 61 |
|
| 62 |
Problem: Fakeauth on a WRT54G with WEP (shared authentication) doesn't work. |
| 63 |
Solution: None at this time (we'll try to fix it in an upcoming release). |
| 64 |
|
| 65 |
|
| 66 |
Airolib-ng |
| 67 |
---------- |
| 68 |
|
| 69 |
Problem: On windows only, opening/creating a database doesn't work when airolib-ng is in directories containing |
| 70 |
special characters like 'ç', 'é', 'è', 'à', ... (directories containing spaces are not affected). |
| 71 |
Reason: It's a SQLite issue. |
| 72 |
Solution: Rename the directory or move the database into another directory. |
| 73 |
|
| 74 |
|
| 75 |
Airodump-ng |
| 76 |
----------- |
| 77 |
|
| 78 |
Problem: Airodump-ng stop working after some time. |
| 79 |
Solution 1: You may have a network manager running that puts back the card in managed mode. |
| 80 |
You'll have to disable it (the fastest solution is killing the process) then restart airodump-ng. |
| 81 |
Solution 2: See Problem 3 of Madwifi-ng. |
| 82 |
|
| 83 |
Problem: On windows, it doesn't display a list of adapters like the old 0.X |
| 84 |
Solution: It requires you to develop your own DLL. |
| 85 |
|
| 86 |
Problem: Handshake is not captured/detected |
| 87 |
Reason: You might be too far and your signal is bad (or too close with a signal too strong). |
| 88 |
Another possibility is that Airodump-ng didn't detect the handshake properly due to |
| 89 |
being far apart in the capture. |
| 90 |
Solution 1: Check out our tutorial 'WPA Packet Capture Explained' in the wiki. |
| 91 |
Solution 2: Try running Aircrack-ng on your capture, it might detect the capture. |
| 92 |
Solution 3: Check out our wpaclean tool. |
| 93 |
Note: It will be fixed in an upcoming release. |
| 94 |
|
| 95 |
Cygwin |
| 96 |
------ |
| 97 |
|
| 98 |
Problem: /usr/include/sys/reent.h:14:20: fatal error: stddef.h: No such file or directory |
| 99 |
Solution: It happens because the gcc and g++ version are different. Make sure they are the same. |
| 100 |
|
| 101 |
Sample files |
| 102 |
============ |
| 103 |
|
| 104 |
wep.open.system.authentication.cap: |
| 105 |
It shows a connection (authentication then association) to a WEP network (open authentication). |
| 106 |
|
| 107 |
wep.shared.key.authentication.cap: |
| 108 |
It shows a connection (authentication then association to a WEP network (shared authentication). |
| 109 |
The difference with open authentication is that the client has to encrypt a challenge text |
| 110 |
and send it back (encrypted) to the AP to prove it has the right key. |
| 111 |
|
| 112 |
wpa.cap: |
| 113 |
This is a sample file with a WPA handshake. It is located in the test/ directory of the install files. |
| 114 |
The passphrase is 'biscotte'. Use the password file (password.lst) which is in the same directory. |
| 115 |
|
| 116 |
wpa2.eapol.cap: |
| 117 |
This is a sample file with a WPA2 handshake. |
| 118 |
It is located in the test/ directory of the install files. |
| 119 |
The passphrase is '12345678'. Use the password file (password.lst) which is in the same directory. |
| 120 |
|
| 121 |
test.ivs (http://download.aircrack-ng.org/wiki-files/other/test.ivs): |
| 122 |
This is a 128 bit WEP key file. |
| 123 |
The key is AE:5B:7F:3A:03:D0:AF:9B:F6:8D:A5:E2:C7. |
| 124 |
|
| 125 |
wep_64_ptw.cap (http://dl.aircrack-ng.org/ptw.cap): |
| 126 |
This is a 64 bit WEP key file suitable for the PTW method. |
| 127 |
The key is '1F:1F:1F:1F:1F'. |
| 128 |
|
| 129 |
wpa-psk-linksys.cap: |
| 130 |
This is a sample file with a WPA1 handshake along with some encrypted packets. |
| 131 |
Useful for testing with airdecap-ng. The password is 'dictionary'. |
| 132 |
|
| 133 |
wpa2-psk-linksys.cap: |
| 134 |
This is a sample file with a WPA2 handshake along with some encrypted packets. |
| 135 |
Useful for testing with airdecap-ng. The password is 'dictionary'. |
| 136 |
|
| 137 |
wps2.0.pcap: |
| 138 |
This is a test file with WPS 2.0 beacon. |
| 139 |
|
| 140 |
password.lst and password-2.lst: |
| 141 |
This is a sample wordlist for WPA key cracking. More wordlists can be found at |
| 142 |
https://www.aircrack-ng.org/doku.php?id=faq#where_can_i_find_good_wordlists |
| 143 |
|
| 144 |
password.db |
| 145 |
This is a sample airolib-ng database for WPA key cracking. |
| 146 |
|
| 147 |
pingreply.c |
| 148 |
Replies to all ping requests. Useful for testing sniffing/injecting packets with airtun-ng. |
| 149 |
|
| 150 |
Chinese-SSID-Name.pcap |
| 151 |
Contains a beacon with an SSID displayed in Chinese. |
| 152 |
|
| 153 |
verify_inject.py |
| 154 |
Testing DNS requests using airtun-ng. |
| 155 |
|
| 156 |
n-02.cap: |
| 157 |
This is a test file with 802.11X-2004 AES-128-CMAC handshake. |
| 158 |
Useful for testing with aircrack-ng. The password is 'bo$$password'. |
| 159 |
|
| 160 |
test-pmkid.pcap: |
| 161 |
This is a test file with PMKID. Passphrase for 'WLAN-771698' is 'SP-91862D361' |
| 162 |
|
| 163 |
test1.pcap: |
| 164 |
This is another test file with PMKID. Passphrase for the network |
| 165 |
'ogogo' is '15211521' |
| 166 |
|
| 167 |
StayAlfred.hccapx: |
| 168 |
Hashcat HCCAPx file with WPA handshake. |
| 169 |
Passphrase for 'StayAlfred' ESSID is 'staytogether' |
| 170 |
|
| 171 |
wpa3-psk.pcap: |
| 172 |
WPA3 PSK SAE authentication. Passphrase for the network |
| 173 |
'WPA3-Network' is 'abcdefgh' |
| 174 |
|
| 175 |
More sample pcap are available from Wireshark: |
| 176 |
https://wiki.wireshark.org/SampleCaptures#Wifi_.2F_Wireless_LAN_captures_.2F_802.11 |