Aircrack-ng

User Tools

Site Tools

Trace:
simple_wep_crack

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
simple_wep_crack [2008/12/28 15:39] – Added additional step for injection testing darkaudaxsimple_wep_crack [2009/09/26 14:36] – Fixed typos darkaudax
Line 1: Line 1:
 ====== Tutorial: Simple WEP Crack ====== ====== Tutorial: Simple WEP Crack ======
-Version: 1.09 December 28, 2008\\+Version: 1.10 September 26, 2009\\
 By: darkAudax By: darkAudax
  
Line 21: Line 21:
   * You are physically close enough to send and receive access point packets.  Remember that just because you can receive packets from the access point does not mean you may will be able to transmit packets to the AP.  The wireless card strength is typically less then the AP strength.  So you have to be physically close enough for your transmitted packets to reach and be received by the AP.  You should confirm that you can communicate with the specific AP by following [[injection_test#hidden_or_specific_ssid|these instructions]].   * You are physically close enough to send and receive access point packets.  Remember that just because you can receive packets from the access point does not mean you may will be able to transmit packets to the AP.  The wireless card strength is typically less then the AP strength.  So you have to be physically close enough for your transmitted packets to reach and be received by the AP.  You should confirm that you can communicate with the specific AP by following [[injection_test#hidden_or_specific_ssid|these instructions]].
   * There is at least one wired or wireless client connected to the network and they are active.  The reason is that this tutorial depends on receiving at least one ARP request packet and if there are no active clients then there will never be any ARP request packets.   * There is at least one wired or wireless client connected to the network and they are active.  The reason is that this tutorial depends on receiving at least one ARP request packet and if there are no active clients then there will never be any ARP request packets.
-  * You are using v0.9 of aircrack-ng. If you use a different version then some of the comman options may have to be changed.+  * You are using v0.9 of aircrack-ng. If you use a different version then some of the common options may have to be changed.
  
 Ensure all of the above assumptions are true, otherwise the advice that follows will not work.  In the examples below, you will need to change "ath0" to the interface name which is specific to your wireless card. Ensure all of the above assumptions are true, otherwise the advice that follows will not work.  In the examples below, you will need to change "ath0" to the interface name which is specific to your wireless card.
Line 130: Line 130:
  
 Where: Where:
-  *-9 means injectin test+  *-9 means injection test
   *-e teddy is the wireless network name   *-e teddy is the wireless network name
   *-a 00:14:6C:7E:40:80 is the access point MAC address   *-a 00:14:6C:7E:40:80 is the access point MAC address
Line 194: Line 194:
   *-e teddy is the wireless network name   *-e teddy is the wireless network name
   *-a 00:14:6C:7E:40:80 is the access point MAC address   *-a 00:14:6C:7E:40:80 is the access point MAC address
-  *-h 00:0F:B5:88:AC:82 is our card MAC addresss+  *-h 00:0F:B5:88:AC:82 is our card MAC address
   *ath0 is the wireless interface name   *ath0 is the wireless interface name
  
Line 240: Line 240:
   *Some access points are configured to only allow selected MAC addresses to associate and connect.  If this is the case, you will not be able to successfully do fake authentication unless you know one of the MAC addresses on the allowed list.  If you suspect this is the problem, use the following command while trying to do fake authentication.  Start another session and...   *Some access points are configured to only allow selected MAC addresses to associate and connect.  If this is the case, you will not be able to successfully do fake authentication unless you know one of the MAC addresses on the allowed list.  If you suspect this is the problem, use the following command while trying to do fake authentication.  Start another session and...
  
-Run: tcpdump -n -vvv -s0 -e -i <interface name> | grep -i -E "(RA:<MAC addreess of your card>|Authentication|ssoc)"+Run: tcpdump -n -vvv -s0 -e -i <interface name> | grep -i -E "(RA:<MAC address of your card>|Authentication|ssoc)"
  
 You would then look for error messages. You would then look for error messages.
simple_wep_crack.txt · Last modified: 2018/03/11 20:13 by mister_x