Differences

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

--- arp-request_reinjection [2007/11/08 22:40] – reformat troubleshooting and added more. darkaudax
+++ arp-request_reinjection [2010/11/21 16:08] (current) – typos sleek
@@ Line 12: / Line 12: @@
    * [[http://www.pcmag.com/encyclopedia_term/0,2542,t=ARP&i=37988,00.asp|PC Magazine: Definition of ARP]]
    * [[http://en.wikipedia.org/wiki/Address_resolution_protocol|Wikipedia: Address Resolution Protocol]]
-   * [[http://technet2.microsoft.com/windowsserver/en/library/7b77bb1b-5c57-408f-907f-8b474203a5331033.mspx?pf=true|Microsft Technet: Address Resolution Protocol (ARP)]]
+   * [[http://technet.microsoft.com/en-us/library/cc758357(WS.10).aspx|Microsft Technet: Address Resolution Protocol (ARP)]]
    * [[http://tools.ietf.org/html/rfc826|RFC 826]]
@@ Line 27: / Line 27: @@
   *ath0 is the wireless interface name\\
-Replaying a previous arp replay.  This is a special case of the [[interactive_packet_replay|interactive packet replay attack]].  It is presented here since it is complementary to the ARP request replay attack.
+There are two methods of replaying an ARP which was previously injected.  The first and simplest method is to use the same command plus the "-r" to read the output file from your last successful ARP replay.
+   aireplay-ng -3 -b 00:13:10:30:24:9C -h 00:11:22:33:44:55 -r replay_arp-0219-115508.cap ath0
+Where:\\
+  *-3 means standard arp request replay\\
+  *-b 00:13:10:30:24:9C is the access point MAC address\\
+  *-h 00:11:22:33:44:55 is the source MAC address (either an associated client or from fake authentication)\\
+  *-r replay_arp-0219-115508.cap is the name of the file from your last successful ARP replay\\
+  *ath0 is the wireless interface name\\
+The second method is a special case of the [[interactive_packet_replay|interactive packet replay attack]].  It is presented here since it is complementary to the ARP request replay attack.
    aireplay-ng -2 -r replay_arp-0219-115508.cap ath0
@@ Line 40: / Line 51: @@
 For all of these examples, use [[airmon-ng]] to put your card in monitor mode first.  You cannot inject packets unless it is in monitor mode.
-For this attack, you need either the MAC address of an associated client , or a fake MAC from [[fake_authentication|attack 1]].  The simplest and easiest way is to utilize the MAC address of an associated client.  This can be obtain via [[airodump-ng]].  The reason for using an associated MAC address is that the access point will only accecpt and repeat packets where the sending MAC address is "associated".
+For this attack, you need either the MAC address of an associated client , or a fake MAC from [[fake_authentication|attack 1]].  The simplest and easiest way is to utilize the MAC address of an associated client.  This can be obtain via [[airodump-ng]].  The reason for using an associated MAC address is that the access point will only accept and repeat packets where the sending MAC address is "associated".
 You may have to wait for a couple of minutes, or even longer, until an ARP request shows up.  This attack will fail if there is no traffic.
@@ Line 54: / Line 65: @@
    Read 11978 packets (got 7193 ARP requests), sent 3902 packets...
-Initally the last line will look similar to:
+Initially the last line will look similar to:
    Read 39 packets (got 0 ARP requests), sent 0 packets...
@@ Line 87: / Line 98: @@
    Sent 3181 packets...
+As well, you can alternatively use per the Usage Section above:
+   aireplay-ng -3 -b 00:13:10:30:24:9C -h 00:11:22:33:44:55 -r replay_arp-0219-115508.cap ath0
 At this point, if you have not already done so, start [[airodump-ng]] to capture the IVs being generated.  The data count should be increasing rapidly.
@@ Line 97: / Line 112: @@
 ==== I am injecting but the IVs don't increase! ====
-See [[http://aircrack-ng.org/doku.php?id=i_am_injecting_but_the_ivs_don_t_increase|Tutorial: I am injecting but the IVs don't increase!]]
+See [[i_am_injecting_but_the_ivs_don_t_increase|Tutorial: I am injecting but the IVs don't increase!]]
 ==== I get 'Read XXXXX packets (got 0 ARP requests), sent 0 packets...(0 pps)' - Why it doesn't send any packets? ====