Speeding Up WEP Hacking : ARP request replay attack
Now if you have followed the basic WEP hacking tutorial, and optionally have also read the basic troubleshooting guide, then you are ready to proceed to the stage where you follow an intermediate level hacking tutorial. In this tutorial, we will look at the intricate details of what is happening and approach the complicated methods and concepts.
So basically you have 2 choices. First, you can buy a new external wireless adapter (no referral links here). Secondly, you can side install Kali with Windows or run it via a USB. A virtual machine can only use computer hardware if it is externally connected via USB. Now there is another catch here. The internal adapters, almost all of them, don’t support injection. This is extremely important for speeding up wireless hacking. So if you really want to go in depth of wireless hacking, then its time to buy an external adapter or two (the more the better). If that’s not a possibility, you might want to spend hours trying to get a driver which might make your internal adapter support injection (I don’t know anyone who succeeded in this, but it might be possible).
Check Injection Support
airmon-ng start wlan0 [or wlan1]
Puts your wireless adapter in monitor mode. From now we’ll refer to wlan0/wlan1 as mon0
airserv-ng -d mon0
aireplay-ng -9 127.0.0.1:666
Check Signal Strength
Now we will hack the digisol network. Make a note of the BSSID of the network you want to hack. A good practice is to store all the information gathered in any text editor. We should, at this stage, take a note of following:-
- ESSID – DIGISOL
- BSSID – 00:17:7C:22:CB:80
- CH (channel) – 2
- Mac address of genuine users connected to the network:
- Interface : wlan1 – referred to as mon0
airodump-ng mon0 -c 2
This will make the wireless card only read packets in the channel no. 2, on which our target network is.
Now to test the network, type the following code-
aireplay-ng --test -e DIGISOL -a 00:17:7C:22:CB:80 mon0
The last time we checked whether the wireless card had the capability to inject packets. We tested it on our own computer. This time, we actually injected packets into the target computer. If this worked, then it’s pretty good news, and it means that you are most probably going to be able to hack this network. The last line 30/30 : 100% determines how good the strength of the signal is. A very high percentage is a good sign, and 100 is ideal.
airodump-ng -c 2 --bssid 00:17:7C:22:CB:80 -w dump mon0
Now the output will be saved in a file dump-01.cap
Now we can keep this terminal running and it will keep saving the packets. [In the previous tutorial we did only 2 things, capture the packet, i.e this step, and crack it, i.e. the step we are going to do last. While it makes our work easier to just follow two steps, it also makes the process much more time consuming, since we are simply a passive packet listener, who is not doing anything]
Speeding Things Up
aireplay-ng -1 0 -e DIGISOL -a 00:17:7C:22:CB:80 mon0
ARP request replay mode
aireplay-ng -3 -b 00:17:7C:22:CB:80 mon0
Now you’ll have to wait for some time till it gets an ARP request. As soon as it gets one, the terminal will sort of explode. And the data packets will start filling in with Godspeed. Now this is the part where an active user on the network is absolutely necessary.
After some time I had enough packets to crack almost any network
Cracking the network
After pressing enter, you will have a list of networks and you’ll be prompted to select which one of them to hack. In my case there was just one network, so I couldn’t get that screen, or a screenshot. The password was cracked in less than a second.
So finally you have obtained the password of the network you were trying to hack.
1) When you start the monitor mode, specify the channel –
usage: airmon-ng [channel or frequency]
Your code : airmon-ng start wlan0 6
Substitute 6 with the required channel.
2) While starting airodump, specify the channel
airodump-ng mon0 -c 6
I was facing this problem when my mon0 kept hopping from one channel to the other, and the second step alone solved my problem. If your airmon-ng assigns itself a fixed channel on its own will, without you even specifying it, then the problem might be more complicated. If the above steps don’t solve the problem, take a look here – http://ubuntuforums.org/showthread.php?t=1598930