search

LostCursor / reaver-wps

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

no automatic delay on 2 netgear routers; tries same pin for 5 mins then resumes normal for 2 min; loops. #82

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

reaver -i mon0 -b 00:26:F2:96:80:61 -c 1 -vv

No automatic delay when AP locks WPS pin attempts.
Reaver tries the same pin for 5 minutes then tries different ones for only 
about 2 minutes, and does this over and over again. Same behavior on 2 
different netgear routers.

Is there a work around to speed things up?

Other linksys and d-links routers worked as expected. 

BT5 64, rtl8187, r65

Original issue reported on code.google.com by reaverwe...@gmail.com on 5 Jan 2012 at 10:13

Attachments:

GoogleCodeExporter commented 8 years ago 
Automatic delay is supposed to be removed in r65. Can't really help with the 
problem though. What are the error messages you get during the 5mins and 2mins? 
You could try --ignore-locks and see if that helps. You can time your errors 
and then change your --lock-delay to cater to your routers.

Original comment by philippe...@hotmail.com on 5 Jan 2012 at 4:07

GoogleCodeExporter commented 8 years ago 
Looking at the beacon packets, the problem is that the AP is not reporting that 
it has locked WPS attempts, so Reaver does not wait for the AP to be unlocked. 
Five minute timeout periods are common (from what I've seen) on Netgears, so 
I'm guessing the AP is locking WPS and just not reporting it.

Letting Reaver continuously re-try the same pin until WPS is unlocked does not 
seem to be having any adverse affect, but you'd like you can specify custom 
timing/sleep options with -x and -r.

Original comment by cheff...@tacnetsol.com on 5 Jan 2012 at 4:16