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.

Sign up for GitHub

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

Jump to bottom

Reaver doesn't detect when rate limiting has stopped. #24

Closed
GoogleCodeExporter opened this issue Apr 15, 2016 · 1 comment
Closed

Reaver doesn't detect when rate limiting has stopped. #24

GoogleCodeExporter opened this issue Apr 15, 2016 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

A few minutes into the attack, Reaver detects rate limiting. After about 20 
minutes it is still detecting rate limiting.

However, if I quit Reaver and restart the attack, it will start trying pins 
again successfully.


Ubuntu 11.10 64 bit
rtl8187
Reaver r20

Original issue reported on code.google.com by rtstanif...@gmail.com on 30 Dec 2011 at 4:09
@GoogleCodeExporter
Copy link
Author 

Dup of issue #22.

Original comment by cheff...@tacnetsol.com on 30 Dec 2011 at 4:16

  • Changed state: Duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter