Aircrack-ng

User Tools

Site Tools

Trace:
arp-request_reinjection

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
Next revisionBoth sides next revision
arp-request_reinjection [2007/04/08 16:51] – darkaudaxarp-request_reinjection [2007/04/18 20:16] – darkaudax
Line 30: Line 30:
   *-r replay_arp-0219-115508.cap is the name of the file from your last successful ARP replay\\   *-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\\ 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: 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: The system responds:
Line 84: Line 87:
    Sent 3181 packets...    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 ===== ===== Usage Tips =====
arp-request_reinjection.txt · Last modified: 2010/11/21 16:08 by sleek