Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AP Rate Limiting - Reaver #719

Open
GoogleCodeExporter opened this issue Mar 19, 2016 · 2 comments
Open

AP Rate Limiting - Reaver #719

GoogleCodeExporter opened this issue Mar 19, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

This is more of a general question for the Reaver experts.

While trying to dial in my delay and lockout times for Reaver I noticed that 
setting the lockout delay to 3600 or 1 hour seems to keep the router healthy 
(mainly century link routers). By healthy I mean not permanently locking wps. 
My question is, does Reavers AP rate limiting detection feature also set off 
the routers AP rate limiting? When leaving it on auto to check every 60 seconds 
it seems to end up in a permanent lockout or manages to execute one pin per 3-4 
hours. When leaving the lockout delay to one hour Reaver can continuously bang 
out 3-8 pins before lockout every hour. I have tried this on multiple routers 
and the results seem to be about even. 



Original issue reported on code.google.com by dan...@gmail.com on 26 Apr 2015 at 4:44

@GoogleCodeExporter
Copy link
Author

Shameless self bump. Seriously does nobody know? Or is this in the wrong 
section?

Original comment by dan...@gmail.com on 28 Apr 2015 at 3:42

@GoogleCodeExporter
Copy link
Author

script of Muskette break it?
https://code.google.com/p/reaver-wps/issues/detail?id=675

Original comment by deltomaf...@gmail.com on 7 Aug 2015 at 3:28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant