Differences

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

--- arp-request_reinjection [2007/04/08 16:51] – darkaudax
+++ arp-request_reinjection [2007/05/25 00:03] – added alternate attack method darkaudax
@@ Line 30: / Line 30: @@
   *-r replay_arp-0219-115508.cap is the name of the file from your last successful ARP replay\\
 ath0 is the wireless card interface name\\
@@ Line 58: / Line 61: @@
 The second example we will look at is reusing the captured ARP from the example above.  You will notice that it said the ARP requests were being saved in "replay_arp-0219-123051.cap".  So rather then waiting for a new ARP, we simply reuse the old ones with the "-r" parameter:
-   aireplay-ng -2  -r replay_arp-0219-123051.cap ath0
+   aireplay-ng -2 -r replay_arp-0219-123051.cap ath0
 The system responds:
@@ Line 84: / Line 87: @@
    Sent 3181 packets...
-At this point, if you have not already done so, start [[airmon-ng]] to capture the IVs being generated.  They data count should be inscreasing rapidly.
+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.
 ===== Usage Tips =====
 When you are testing at home, to generate an ARP packet to initiate the ARP injection, simply ping a non-existent IP on your network.
@@ Line 96: / Line 100: @@
 Also see the general aireplay-ng troubleshooting ideas: [[aireplay-ng#usage_troubleshooting|aireplay-ng usage troubleshooting]].
+Although not a direct troubleshooting tip for the arp request reinjection attack, if you are unable to get the attack to work or there are no arp request packets coming from the access point, there is an alternate attack you should consider:
+  * [[interactive_packet_replay#other_examples|-p 0841 method]]: This technique allows you to reinject any data packet received from the access point and generate IVs.