r92 stops trying PINs after a few minutes

[GoogleCodeExporter]

A few things to consider before submitting an issue:

0. We write documentation for a reason, if you have not read it and are
having problems with Reaver these pages are required reading before
submitting an issue.
1. Reaver will only work if your card is in monitor mode.  If you do not
know what monitor mode is then you should learn more about 802.11 hacking
in linux before using Reaver.
2. Using Reaver against access points you do not own or have permission to
attack is illegal.  If you cannot answer basic questions (i.e. model
number, distance away, etc) about the device you are attacking then do not
post your issue here.  We will not help you break the law.
3. Please look through issues that have already been posted and make sure
your question has not already been asked here: http://code.google.com/p
/reaver-wps/issues/list
4. Often times we need packet captures of mon0 while Reaver is running to
troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap).  Issue
reports with pcap files attached will receive more serious consideration.

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.)

Latest svn r92.  The error was not manifested on my previous version r90.

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

Ubuntu 11.10

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

Card is in monitor mode w/ airmon-ng start wlan0 and capture was already 
ongoing on mono using reaver r90.

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

Signal strength is admittedly very low (~ -82 dBm).  But PINs are successfully 
negotiated and the process did not stop on r90, just a few repeated trials on 
the same PIN every now and then, and successfully continued to 64%.

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

It is an old D-Link AP, but I am not sure about the model number.

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

 sudo reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv -c x -a
(with masked MAC and channel)

6. Please describe what you think the issue is.

Reaver gives up and returns to the command line with any error or warning.  It 
quits every time a run it.  And the time from execution to quit is 
approximately the same every time, possibly the same number of PIN tests.  See 
output with -v to see how many PINs are tried before quitting.  Not a lot of 
PINs tried before quitting.  Again, previous version r90 was not quitting.

7. Paste the output from Reaver below.

As soon as I updated to svn r92 I noticed that the ongoing process would stop 
and reaver would quit without any warning messages, just back to the command 
line.  So I added the second -v to get a more detailed output and it did it 
again.  Here is the output with -vv.

[+] Sending WSC NACK
[+] Trying pin 70355673
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 33665672
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
myname@vubuntu:~/src/reaver$

And here is the output with just one -v (longer period of time):

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

[+] Restored previous session
[+] Waiting for beacon from xx:xx:xx:xx:xx:xx
[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxxxxxx)
[+] Trying pin 21155673
[+] Trying pin 23735675
[+] Trying pin 34935675
[+] Trying pin 70355673
[+] Trying pin 33665672
[+] Trying pin 85885677
[+] 64.93% complete @ 2012-01-16 02:21:13 (10 seconds/attempt)
[+] Trying pin 71325675
[+] Trying pin 02955674
[+] Trying pin 02955674
[+] Trying pin 02955674
[+] Trying pin 67965670
[+] 64.95% complete @ 2012-01-16 02:22:08 (13 seconds/attempt)
[+] Trying pin 06395674
myname@vubuntu:~/src/reaver$

And, here is a second, consecutive run with -v (showing about same length 
before quitting):

[+] Restored previous session
[+] Waiting for beacon from xx:xx:xx:xx:xx:xx
[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxxxxxx)
[+] Trying pin 26275673
[+] Trying pin 20485672
[+] Trying pin 23455672
[+] Trying pin 94765670
[+] Trying pin 42505679
[+] Trying pin 93525671
[+] 65.03% complete @ 2012-01-16 02:29:43 (9 seconds/attempt)
[+] Trying pin 17005678
[+] Trying pin 64955674
[+] Trying pin 62695671
[+] Trying pin 60345677
[+] Trying pin 57175676
[+] 65.07% complete @ 2012-01-16 02:30:06 (7 seconds/attempt)
[+] Trying pin 56065671
myname@vubuntu:~/src/reaver$ 

Original issue reported on code.google.com by vsil...@gmail.com on 16 Jan 2012 at 8:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I am getting the same issue. Strangly though, if I revert back to r91 the issue 
still occurs but it is not as frequent.

Original comment by kahakki...@gmail.com on 16 Jan 2012 at 10:41

[GoogleCodeExporter]

Reaver is actually seg faulting. Had the same thing happen to me last night, 
looking in to it now. Appears to happen after re-transmitting the M2 packet and 
while trying to build an M4 packet.

Original comment by cheff...@tacnetsol.com on 16 Jan 2012 at 12:10

• Changed state: Started

[GoogleCodeExporter]

Ah, cool. Thanks :)

Original comment by kahakki...@gmail.com on 16 Jan 2012 at 12:16

[GoogleCodeExporter]

Fixed.

Original comment by cheff...@tacnetsol.com on 16 Jan 2012 at 3:13

• Changed state: Fixed

[GoogleCodeExporter]

Hrm....spoke too soon.

Original comment by cheff...@tacnetsol.com on 16 Jan 2012 at 3:40

• Changed state: Started

[GoogleCodeExporter]

OK, now it's fixed. :)

Original comment by cheff...@tacnetsol.com on 16 Jan 2012 at 4:46

• Changed state: Fixed