Differences

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

--- arp-request_reinjection [2010/03/06 17:42] – updated arp link from microsoft website mister_x
+++ arp-request_reinjection [2010/11/21 16:08] (current) – typos sleek
@@ Line 51: / 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 65: / 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...