This is an old revision of the document!
Aircrack is very simple to use once you know the concept. This flowchart will hopefully teach you the concept behind simple wifi cracking. You will want to keep airodump-ng running to collect data, and then run your attacks. Each attack will use aireplay-ng, and the ultimate goal is to generate data on the network… most commonly ARP data. In this tutorial I assume you have read the wiki and am familiar with the different tools and attacks. This is not a hand-holding tutorial, this is a theory tutorial. This tutorial tells you WHEN to use an attack, not the specifics of the attack (as they are already written in the wiki). Remember, this is for simple wep cracking, where the goal is to recover the wep-key for the network. It tells you when to use the tools, not how. See the next section for how to use the tools.
Read the flowchart, read the wiki entries for the different tools I've listed, and use the flowchart to go step-by-step until you reach an end.
Running airodump-ng with no parameters will show you every AP in your area. You will want to use a few parameters to single out the AP you are trying to crack, so you only collect the information you need.
aircrack-ng -c 6 --bssid 11:22:33:44:55:66 -w output
|-c 6||Sets channel to 6, change the number to whatever channel your AP is on. Very important, so you are not chan hopping.|
|–bssid 11:22:33:44:55:66||Sets the BSSID to single out. This is set to your AP's MAC Address (seen in airodump-ng)|
|-w output||Sets the output file, this will start outputting data to output-##.cap|
See the following URL's for compatibility information:
If you can not associate to your AP, you need to turn off WPA filtering, or make sure you have turned off mac filtering. If you have mac filtering on, make sure your mac address is not spooofed and is in the list of allowed clients.
Since clients are connected, you will first want to run the arp interactive (-3) attack, and leave it running so it can listen for the ARP packet which will be generated when you deauth the client who is connected. By deauthing, you will generate an arp which can be re-injected, thus generating data on the network.
In order to crack anything, the AP has to send out atleast 1 packet. This packet will be used on the chopchop (-4) or fragmentation (-5) attack, or hopefully the arpinteractive (-3) attack. If the AP is not sending out any data, it likely means no one is connected to the AP via wired or wireless. You will just have to wait, keep airodump-ng running with the -w switch (to output data) overnight, and you may get lucky.
The point of cracking is to generate data. You can generate data in Section 4, but sometimes there are no clients connected to wifi, but the AP is still sending out data. In this case, you will want to capture the data that the AP is sending out, and use it to determine a valid XOR keystream (basically a file which allows you to create a packet with out knowing the key). The two attacks for this are “fragmentation” and “chop-chop”. Fragmentation is quickest, but it doesn't always work on every AP. Chop-chop usually works, but you have to have a good connection to the AP (be close to the AP).
For fragmetnation: try a few more packets sent out by the AP. Try spoofing your mac address to the source address in the packet. If this still doesn't work, the AP may not be vulnerable to the frag attack.
For the Chop-Chop attack, you really need to have a good connection to the AP, you have to be close. You should choose a packet that is very small, you only need about a 70 byte packet… this reduces the number of packets required to generate the xor keystream (choosing a larger file takes longer and therefore is more likely to fail).
We have an XOR keystream meaning we can make any packet we want, as long as we have enough bytes in the keystream. For an ARP packet (packetforge -0), 70 is enough bytes which is the shortest packet you'll generally see from the AP. Generate an ARP packet using packetforge, you may use arp amplification if you like. For the -l and -k swithces I generally use 255.255.255.255 and it works just fine.
If you have done things right, you should start to see the #/s and “Data” fields in airodump-ng climb to high numbers. While this is going on, you will want to run aircrack-ng on the .cap files you are creating with airodump-ng. You may also use wildcards if you have run multiple airodump sessions. For example:
This will open up any file starting with “output-” and ending with “.cap”.
There are many reason that you wont be able to.
I hope you have found this tutorial helpful. Originally written by “matts”. Thank you.