ipw2200_generic
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ipw2200_generic [2007/08/29 05:32] – drio | ipw2200_generic [2007/08/29 18:56] – drio | ||
---|---|---|---|
Line 44: | Line 44: | ||
documents recommend to start [[http:// | documents recommend to start [[http:// | ||
There is another option: [[http:// | There is another option: [[http:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
Line 73: | Line 77: | ||
When I used [[http:// | When I used [[http:// | ||
- | We need the rtap0 up and running. | + | We need the rtap0 up and running. |
- | # | + | # |
- | # | + | |
+ | That's the method I would recommend. But, if you are using the latest version of airodump-ng (we'll use it in the next section) you can | ||
+ | tell the program to creat the rtap0 device for you: | ||
+ | |||
+ | # | ||
+ | |||
+ | We'll talk it in the next section. | ||
Ok, so we have verified that we have an ipw2200 card and that Linux can talk to it. | Ok, so we have verified that we have an ipw2200 card and that Linux can talk to it. | ||
Line 99: | Line 109: | ||
# ifconfig eth1 up hw ether 00: | # ifconfig eth1 up hw ether 00: | ||
+ | |||
Line 108: | Line 119: | ||
# iwconfig eth1 essid < | # iwconfig eth1 essid < | ||
- | Due to some limitations with the firmware we have to force a fakekey to ensure the airdump-ng tools work properly. | + | Due to some limitations with the firmware we have to force a fakekey |
ESSID is the name of the wireless network of our target AP. Channel is the wireless channel. | ESSID is the name of the wireless network of our target AP. Channel is the wireless channel. | ||
+ | |||
Line 118: | Line 130: | ||
In another window, we start collecting data: | In another window, we start collecting data: | ||
- | # airodump-ng --bssid <AP MAC> -w dump rtap0 | + | # airodump-ng |
Notice how we use rtap0 as a input interface. Also, all these commands we are going to be running generate output files. So it is a good idea | Notice how we use rtap0 as a input interface. Also, all these commands we are going to be running generate output files. So it is a good idea | ||
to create a new directory and to run all of them from there. | to create a new directory and to run all of them from there. | ||
+ | |||
+ | As we said before, if you are running the latest version of airodump-ng, | ||
+ | |||
Line 128: | Line 143: | ||
Now it is time to do some injection. In a new window we will launch the chopchop attack: | Now it is time to do some injection. In a new window we will launch the chopchop attack: | ||
- | # aireplay-ng -4 -a <AP MAC> -h 00: | + | # aireplay-ng -4 -a <AP MAC> -h 00: |
Note the modifier "-i rtap0." | Note the modifier "-i rtap0." | ||
Line 137: | Line 152: | ||
Make sure there are no errors reported after using aireplay. If the attack doesn' | Make sure there are no errors reported after using aireplay. If the attack doesn' | ||
vulnerable to the chopchop attack. I also received an error stating the checksum didn't match. I just re-ran aireplay and it was fine. | vulnerable to the chopchop attack. I also received an error stating the checksum didn't match. I just re-ran aireplay and it was fine. | ||
+ | |||
+ | If the attack fails, try to rerun the command again ommiting the "-h <AP MAC>" | ||
+ | |||
+ | |||
+ | |||
+ | |||
Line 145: | Line 166: | ||
Now we will create an arp-request packet using the aquired keysteam file. The " | Now we will create an arp-request packet using the aquired keysteam file. The " | ||
- | They can be any valid IP. The destination | + | If you use valid destination |
- | in the same window we run the chopchop attack: | + | we run the chopchop attack: |
- | # packetforge-ng -0 -a <AP MAC> -h 00: | + | # packetforge-ng -0 -a <AP MAC> -h 00: |
ipw2200_generic.txt · Last modified: 2009/09/26 14:27 by darkaudax