omegakw / reaver-wps

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

0x02, 0x03 errors followed by AP having "null" WPS Lock-Out state for 4 hours after 0.5% completion. #357

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I've succeeded in revealing several of my routers WPS pins and WPA keys using 
reaver; however, the latest one is giving me the most issues. 

After 0.5% of pin attempts are completed in reaver, I begin receiving the 0x02 
and 0x03 errors followed by the "WARNING 10 failed attempts in a row". 

Afterwards I run wash and notice that under WPS-lock beside my AP it says 
"null" (weird!). 
Then, it takes approximately 4 hours for the AP to return to its original 
WPS-Lock state "no" in wash. 

I am then able to retry Brute forcing the pin in reaver only to receive the 
same errors after another 0.5% pin attempts once again. I have tried the -d 
option at -d 16 to avoid 4 hour lock-outs and I still receive these errors. 

The AP signal is excellent.

So I offer a simple question, how do I avoid these 4-hour lockouts after 0.5% 
pin attempts?

Original issue reported on code.google.com by brayma...@gmail.com on 17 Jul 2012 at 7:16

GoogleCodeExporter commented 8 years ago
same here!!!

Original comment by richard....@mymdc.net on 29 Aug 2012 at 3:37