Doesn't timeout when using -N

[GoogleCodeExporter]

Hi,

I am using the latest trunk (r106) with the latest stable drivers from compat 
wireless (patched for negative one issue) and my device has an Intel5100 using 
the iwlwifi driver.

I put the card into monitor mode with airmon-ng then associate it with my AP 
with aireplay-ng.
I then run reaver -i mon0 -b XX:XX;XX:XX:XX:XX -A -N -vv which results in

[+] Trying pin 00055673
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message

Without the -N on the first duplicate M1 message it NACKs and trys again, with 
-N it doesn't appear to timeout when it gets to this state even with -t 1.

With -N between the pausing it does appear to make progress,
[+] Trying pin 00055673
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M3 message
[+] Received M3 message
[+] Received M3 message
[+] Received M3 message
[+] Received M3 message
[+] Received M3 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00065672

Original issue reported on code.google.com by benwhit...@gmail.com on 18 Jan 2012 at 11:26

[GoogleCodeExporter]

What is the time period of the above output? That is, do you receive all of 
those M1 messages very quickly, or are there long pauses in between each 
"Received M1 message"?

Original comment by cheff...@tacnetsol.com on 18 Jan 2012 at 11:35

[GoogleCodeExporter]

They normally will come in a big block very quickly, a few may trickle in after 
that a couple of seconds apart but then nothing more comes in at all. It just 
sits there until I break the program.

That particular one was left for 20minuites.

Original comment by benwhit...@gmail.com on 19 Jan 2012 at 9:54

[GoogleCodeExporter]

Try r107, it should timeout properly now with -N specified.

Original comment by cheff...@tacnetsol.com on 19 Jan 2012 at 2:20

• Changed state: Started

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Disregard my last comment, forgot to do a make clean. Its working fine now 
thanks for the fix.

Original comment by benwhit...@gmail.com on 19 Jan 2012 at 8:28

[GoogleCodeExporter]

BT5 r1

rt2800usb with last compat-wireless driver

revision 107 of reaver 1.4

i can t test a pin i obtain error 0x2 and 0x3 on all AP tested...

BSSID                  Channel       RSSI       WPS Version       WPS Locked    
    ESSID
--------------------------------------------------------------------------------
-------------------------------
00:19:70:66:9A:A6       1            -59        1.0               No            
    Bbox-

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

[+] Switching mon0 to channel 1
[+] Waiting for beacon from 00:19:70:66:9A:A6
[+] Associated with 00:19:70:66:9A:A6 (ESSID: Bbox-A53F04)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
^C
[+] Nothing done, nothing to save.

Original comment by c4n...@gmail.com on 20 Jan 2012 at 12:19

[GoogleCodeExporter]

@ben: Great!

@c4n4rd: It looks like the AP is having problems seeing the packets that Reaver 
is sending; this could be due to a poor receiver in the AP or interference at 
the AP's location. You will probably need to get a better signal from the AP in 
order to run the attack.

Original comment by cheff...@tacnetsol.com on 20 Jan 2012 at 2:24

• Changed state: Fixed