Received M5 message, but the firs half is not correct

[GoogleCodeExporter]

reports with pcap files attached will receive more serious consideration.

I can't attach the file (attachment storage quota exceeded).

Answer the following questions for every issue submitted:

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

1.4

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

Bt5R2

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?

-25 (AP only 30 cm from Wifi card, so that is not a problem)

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

LevelOne WBR-6003

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

./reaver -i mon0 -b <MAC> -vv
Also tried various advanced and optional arguments

6. Please describe what you think the issue is.

The AP sends M5 message on the first tried PIN (12345670), but the first half 
of the PIN is not correct. It works fine if I specify the first half or if I 
try some other (not mine) APs. I think it is an AP issue, but I could be 
mistaken. Maybe there is an option/argument to get past this. I couldn't find 
anything in the other issues.

7. Paste the output from Reaver below.

[?] Restore previous session for 0------------? [n/Y] n
[+] Waiting for beacon from 0---------------
[+] Switching mon0 to channel 1
[+] Associated with 0------------ (ESSID: CrackMe)
[+] 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 M5 message
[+] Sending M6 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 12340002
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M5 message
[+] Sending M6 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 12342228
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
^C

Original issue reported on code.google.com by gospod.a...@gmail.com on 23 Mar 2012 at 8:02