Rate limiting issue on E3200. Possible fix.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. When brute forcing the E3200, after a little while I got the rate limiting 
warning. The message kept displaying for 15 minutes (it might be forever, I 
will let Reaver go infinitely tonight).

Fix / feature request:

Setting the lock delay to 60, quitting and restarting Reaver after the 60 
seconds has elapsed let's me test 4 new pins every single time (a longer delay 
doesn't seem to help getting more PINs, a lower setting gets less or no PINs). 
This is tedious to do, and is a constant behaviour, so maybe something of the 
likes could be implemented? Is Reaver re-authenticating at every start? That 
might be what helps.

Using a 60 second lock delay and automatically re-authenticating afterwards 
would help a lot.

Thank you

Original issue reported on code.google.com by philippe...@hotmail.com on 4 Jan 2012 at 8:01

[GoogleCodeExporter]

Actually, a simple option to re-associate after perceived rate limiting would 
do the trick (if Reaver is actually re-associating).

Original comment by philippe...@hotmail.com on 4 Jan 2012 at 8:08

[GoogleCodeExporter]

This is easily fixed using --ignore-locks. I am very sorry, I had read the 
ReadMe on the wiki, not the actual Reaver help. Using ignore locks, the tool 
displays timeout warnings for about 60seconds and then cracks 4 new pins every 
time.

Please close this issue,
Great work BTW!

Original comment by philippe...@hotmail.com on 4 Jan 2012 at 8:22

[GoogleCodeExporter]

Thanks philippe! There is a bug in Reaver 1.3 that prevents Reaver from 
properly identifying when an AP has unlocked WPS. This has been fixed in the 
SVN code, so you should be able to properly specify a 60 second wait period and 
Reaver will start the attack after 60 seconds.

Original comment by cheff...@tacnetsol.com on 4 Jan 2012 at 12:51

• Changed state: WontFix

[GoogleCodeExporter]

Thank you! r58 properly identifies my AP has unlocked (setting a 60 seconds 
lock-delay). I wish my RT73 device was 5GHz compatible, now :) Keep up the good 
work!

Original comment by philippe...@hotmail.com on 4 Jan 2012 at 8:43