search

seteve / reaver-wps

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

WARNING: 25 successive start failures #147

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 

0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)

reaver 1.4 revision 97

1. What operating system are you using (Linux is the only supported OS)?

backtrack 5R1

2. Is your wireless card in monitor mode (yes/no)?

Yes

3. What is the signal strength of the Access Point you are trying to crack?

70% on windows

4. What is the manufacturer and model # of the device you are trying to
crack?

2wire 2701HG-G

5. What is the entire command line string you are supplying to reaver?

./reaver  -i mon0 -b C8:CD:72:D7:B4:9B -v

6. Please describe what you think the issue is.

7. Paste the output from Reaver below.

reaver continue however to try pins.

+] 37.15% complete @ 2012-01-16 22:06:47 (3 seconds/pin)
[+] Trying pin 40865676
[+] Trying pin 40875675
[+] Trying pin 40885674
[+] Trying pin 40895673
[+] Trying pin 40905679
[!] WARNING: 25 successive start failures
[+] 37.18% complete @ 2012-01-16 22:09:08 (3 seconds/pin)
[+] Trying pin 40905679
[+] Trying pin 40915678
[+] Trying pin 40925677
[+] Trying pin 40935676
[+] Trying pin 40945675
[+] 37.23% complete @ 2012-01-16 22:09:25 (3 seconds/pin)

Original issue reported on code.google.com by voleuse....@gmail.com on 17 Jan 2012 at 3:15

GoogleCodeExporter commented 8 years ago 
Although many of these warnings can be an indication of problems, this happens 
sometimes. If it's just happening occasionally and Reaver keeps going 
afterwards, it's not a big deal.

If you use -vv instead of -v here is what I expect you'd see: when attempting 
pin 40905679 the first time, the WPS transaction does not properly complete (a 
packet probably got dropped/corrupted somewhere) and Reaver terminates the WPS 
session in order to try the pin again. After this, the AP does not respond to 
EAPOL START and/or EAP identity response packets, probably because it did not 
honor Reaver's request to terminate the previous WPS session. Reaver keeps 
trying to initiate a new WPS session though, and eventually the AP's stale 
session times out and it starts accepting new WPS sessions, at which point 
Reaver can start trying pins again.

Original comment by cheff...@tacnetsol.com on 17 Jan 2012 at 3:42