Aircrack-ng

User Tools

Site Tools

Trace:
ipw2200_generic

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
ipw2200_generic [2007/08/29 18:44] – hopping is not a good idea. drioipw2200_generic [2009/05/04 00:12] – Update links to forum mister_x
Line 8: Line 8:
    - More detailed explaination about what we are doing on each step    - More detailed explaination about what we are doing on each step
    - upgrade airo tools from the livecd.    - upgrade airo tools from the livecd.
- 
- 
- 
- 
- 
- 
- 
- 
- 
  
 ===== Introduction ===== ===== Introduction =====
  
-This document is based in this [[http://tinyshell.be/aircrackng/forum/index.php?topic=2077.0|post]] you can find in the [[http://tinyshell.be/aircrackng/forum/index.php|forums]].+This document is based in this [[http://forum.aircrack-ng.org/index.php?topic=2077.0|post]] you can find in the [[http://forum.aircrack-ng.org/index.php|forums]].
  
 When I started using the aircrack-ng tools I did not have the  When I started using the aircrack-ng tools I did not have the 
Line 44: Line 35:
 documents recommend to start [[http://en.wikipedia.org/wiki/Wikipedia:Featured_article_candidates/X_Window_core_protocol|Xwindow]] and open then various xterminals. documents recommend to start [[http://en.wikipedia.org/wiki/Wikipedia:Featured_article_candidates/X_Window_core_protocol|Xwindow]] and open then various xterminals.
 There is another option: [[http://en.wikipedia.org/wiki/GNU_Screen|screen]]. There is another option: [[http://en.wikipedia.org/wiki/GNU_Screen|screen]].
- 
- 
- 
- 
- 
  
 ===== Verify that our ipw2200 card is recognized by the OS (Linux) ===== ===== Verify that our ipw2200 card is recognized by the OS (Linux) =====
Line 89: Line 75:
  
 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.
- 
- 
  
 ===== List available networks =====  ===== List available networks ===== 
Line 101: Line 85:
 === NOTE: === === NOTE: ===
 I am assuming that linux mapped your wireless card under eth1. Most likely you have an ethernet card under eth0. I am assuming that linux mapped your wireless card under eth1. Most likely you have an ethernet card under eth0.
- 
- 
  
 ===== Change the MAC address of our card ===== ===== Change the MAC address of our card =====
Line 109: Line 91:
  
        # ifconfig eth1 up hw ether 00:11:22:33:44:55        # ifconfig eth1 up hw ether 00:11:22:33:44:55
- 
- 
- 
  
 ===== Configure the wireless parameters ===== ===== Configure the wireless parameters =====
Line 119: Line 98:
        # iwconfig eth1 essid <ESSID> channel <#> key s:fakekey mode managed        # iwconfig eth1 essid <ESSID> channel <#> key s:fakekey mode managed
  
-Due to some limitations with the firmware we have to force a fakekey and set managed mode to ensure the airdump-ng tools work properly.+Due to some limitations with the firmware we have to force a fakekey and set managed mode to ensure the aircrack-ng tools work properly.
  
 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.
- 
- 
- 
  
 ===== Collect data with airodump-ng ===== ===== Collect data with airodump-ng =====
Line 136: Line 112:
  
 As we said before, if you are running the latest version of airodump-ng, rtap0 will be created for you automatically in case you didn't before. As we said before, if you are running the latest version of airodump-ng, rtap0 will be created for you automatically in case you didn't before.
- 
  
 ===== Launch the chopchop attack ===== ===== Launch the chopchop attack =====
Line 142: Line 117:
 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:11:22:33:44:55 -i rtap0 eth1+       # aireplay-ng -4 -a <AP MAC> -h 00:11:22:33:44:55 -i rtap0 eth1
  
 Note the modifier "-i rtap0." This tells aireplay to use rtap0 for listening and eth1 for injecting. Also "-4" is the type of attack (chopchop). Note the modifier "-i rtap0." This tells aireplay to use rtap0 for listening and eth1 for injecting. Also "-4" is the type of attack (chopchop).
Line 152: Line 127:
 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>" parameter.
- +
  
 ===== Create the arp request packet ===== ===== Create the arp request packet =====
  
 Now we will create an arp-request packet using the aquired keysteam file. The "-l" and "-k" options are the source IP and destination IP.  Now we will create an arp-request packet using the aquired keysteam file. The "-l" and "-k" options are the source IP and destination IP. 
-They can be any valid IP. The destination can be the gateway (router IP) but the attack run faster if it is an arbitrary IP. This can be run  +If you use valid destination IPs then you will be running an [[arp_amplification|amplification attack]]. This can be run in the same window  
-in the same window we run the chopchop attack:+we run the chopchop attack:
        
-       # packetforge-ng -0 -a <AP MAC> -h 00:11:22:33:44:55 -k 192.168.1.100 -l 192.168.1.101 -y replay_dec-####.xor -w arp-request +     # packetforge-ng -0 -a <AP MAC> -h 00:11:22:33:44:55 -k 192.168.1.100 -l 192.168.1.101 -y replay_dec-####.xor -w arp-request
- +
- +
  
 ===== Send the arp request over and over ===== ===== Send the arp request over and over =====
Line 173: Line 143:
  
       # aireplay-ng -2 -r arp-request eth1       # aireplay-ng -2 -r arp-request eth1
- 
- 
- 
- 
- 
- 
- 
  
 ===== Wait to gather enough IVs ===== ===== Wait to gather enough IVs =====
  
-We have to wait now so airodump-ng gathers enough data (enough IVs) so we can run airocrack-ng.  +We have to wait now so airodump-ng gathers enough data (enough IVs) so we can run aircrack-ng.  
-How many packages we need so airocrack-ng cracks the wep key? It depends. The version of  +How many packages we need so aircrack-ng cracks the wep key? It depends. The version of  
-airocrack-ng that comes with backtrack2 is not the lastest one. There have been a lot of improvements in recent versions  +aircrack-ng that comes with backtrack2 is not the latest one so we need around 1.000.000 of IVs. 
-that have reduced the number of IVs needed. In my experience, I have found 300k (data output) is more than enough. +If we are using the latest version (0.9 and up) 100.000 is enough.
- +
- +
- +
- +
- +
  
 ===== Crack the wep key using aircrack-ng ===== ===== Crack the wep key using aircrack-ng =====
Line 198: Line 155:
 In another window we launch: In another window we launch:
  
-      # aircrack-ng dump*.cap+      # aircrack-ng -z dump*.cap
  
-Depending the number of packages you have gathered, this may take some minutes or you may get the key inmediately.+Depending the number of packages you have gathered, this may take some minutes or you may get the key immediately. 
 +The -z argument tells aircrack-ng to also try the PTW attack. If you version of aircrack-ng doesn't support it, just 
 +omit it.
  
 === NOTE: === === NOTE: ===
Line 207: Line 166:
 wait for more data to be gathered. wait for more data to be gathered.
  
- 
-  
ipw2200_generic.txt · Last modified: 2009/09/26 14:27 by darkaudax