How to get rid of rate limiting :D

[GoogleCodeExporter]

Messing around with reaver I discovered that when the ap limit rate is detected 
and you get locked out you can unlock it again instantly by trying to 
authenticate to the access point ( actually trying to connect via Wcid and 
failing to auth) then the you can begin sending pins again(the limiter is 
aparently reset). I wonder if this can be incorporated fully into Reaver, I 
don't know if it will work on all wifi but it sure did on mine :D
          JC

Original issue reported on code.google.com by jordanc....@gmail.com on 29 Jan 2013 at 9:28

[GoogleCodeExporter]

unlock how via aireplay-ng ?

Original comment by kostad...@yahoo.com on 30 Jan 2013 at 7:13

[GoogleCodeExporter]

No after the lockout i was using the wireless manager to try to connect to
the ap(with a random password), when it fails it must reset the lockout so
i could carry on firing wpa pins.

Original comment by jordanc....@gmail.com on 30 Jan 2013 at 3:52

[GoogleCodeExporter]

nop, it dosn't work for me:
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
over and over again 
:(

Original comment by kostad...@yahoo.com on 2 Feb 2013 at 1:23

[GoogleCodeExporter]

I think I understand what you mean
I was doing (again "I think", cause I'm not sure)
the same trick using aireplay-ng.

In my case (my AP lockout after 5 false attempts for 530sec):

*1st > manualy set the channel for the mon:
# iwconfig  <mon device>    channel <channel #>

*2nd > use aireplay-ng for the association process and sending keep alive 
packets every 60sec (add -A to reaver):
#aireplay-ng  -1 60    -a <AP's BSSID>    -h <mon's mac>    -e <AP's ESSID>    
<mon device>

*3rd >
#reaver   -i <mon device>    -b <AP's BSSID>     -e <AP's ESSID>   -c <channel 
#>    -N -S -A -v

Original comment by i.boud...@gmail.com on 2 Feb 2013 at 3:01

[GoogleCodeExporter]

Yeah i tried on another router and didn't work so must be only on some of
them that it works.

Original comment by jordanc....@gmail.com on 3 Feb 2013 at 12:52

[GoogleCodeExporter]

I found another way!
U should use same MAC as already associated client

Original comment by kostad...@yahoo.com on 15 Feb 2013 at 8:55

[GoogleCodeExporter]

cool does it work on all routers? how many routers have u tested it on

Original comment by jordanc....@gmail.com on 20 Feb 2013 at 6:49

[GoogleCodeExporter]

HI, and MAC how to change :)how to find it, where to see it ... regards

Original comment by m_ili...@abv.bg on 16 Apr 2013 at 7:03

[GoogleCodeExporter]

first put your wireless card off    ifconfig wlan0 down    then
 macchanger -r wlan0    (the -r means it will make a random mac address)
then do     ifconfig wlan0 up     your good to go.

Original comment by jordanc....@gmail.com on 19 Apr 2013 at 9:03