search

allishwell / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

AP rate limiting stuck #155

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
After 0.75% reaver is stuck at that... in my 2 routers.... i tried the reaver 
and re tried next day and still the same matter..??

[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying
[!] WARNING: Detected AP rate limiting, waiting 315 seconds before re-trying

Original issue reported on code.google.com by ermentsa...@gmail.com on 19 Jan 2012 at 10:55

GoogleCodeExporter commented 8 years ago 
Sounds like the AP has locked WPS. Some lock only for a short period of times, 
others lock indefinitely. Some report that they are locked when they really 
aren't - try using the --ignore-locks option. If that doesn't work, then you're 
SOL I'm afraid; Reaver can't brute force pins if the AP is rejecting WPS 
requests.

Original comment by cheff...@tacnetsol.com on 20 Jan 2012 at 2:26