search

Kennyl / reaver-wps

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

AP Lockdown Workaround #70

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. reaver -i mon0 -b[bssid] -L -vv
2.
3.

What is the expected output? What do you see instead?

Reaver associates to AP and begins injecting pins, but AP shuts down WPS 
service after about 16 failed attemps or so. This particular AP requires to be 
rebooted in order to resume WPS service. This is an AP issue, not a Reaver 
issue.
Question: Is it possible to force an AP to reboot remotely? My thought process 
is that this function could be included in Reaver as an option when it detects 
an AP lockdown, it then forces a reboot of the AP and does its 315-second wait 
before resuming the attack. 

Just wanted to throw this out there as a potential workaround for lockdowns.

Thanks for the great work!

What version of the product are you using? On what operating system?

Reaver 1.2, Linux, Backtrack 5 64-bit.

Please provide any additional information below.

Dlink AP, ath5k adapter

Original issue reported on code.google.com by brloz...@comcast.net on 4 Jan 2012 at 3:36