Loops Sending/Receiving Indentity Response

[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:
http://code.google.com/p/reaver-wps/wiki/HintsAndTips
http://code.google.com/p/reaver-wps/wiki/README
http://code.google.com/p/reaver-wps/wiki/FAQ
http://code.google.com/p/reaver-wps/wiki/SupportedWirelessDrivers
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.)

1.4

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

Ubuntu 

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?

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

96

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

sudo reaver -i mon0 -b 00:FE:F4:1D:41:88 -S -L -vv

6. Please describe what you think the issue is.

I ma not sure. It has started properly before but then carried on with the 
following loop.

7. Paste the output from Reaver below.

[+] Waiting for beacon from 00:FE:F4:1D:41:88
[+] Switching mon0 to channel 1
[+] Associated with 00:FE:F4:1D:41:88 (ESSID: BTHub3-GMW2)
[+] 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
As you can see it just loops. It continues to do this and I am really stuck. 
Any help will be much appreciated. I have tried -a -N etc etc.

Original issue reported on code.google.com by mrjackba...@gmail.com on 18 Feb 2013 at 10:31

[GoogleCodeExporter]

Hi,
Please upload network trace and I will have a look at it. This seems to be 
related to the issue I have recently reported (ticket 481) and network trace 
will verify this.
Also, have you ran "wash" against your AP ?

Original comment by marek.pa...@gmail.com on 14 Mar 2013 at 7:33

[GoogleCodeExporter]

low wifi signal in u case!

Original comment by kostad...@yahoo.com on 24 Mar 2013 at 8:46

[GoogleCodeExporter]

I get this exact same issue with BTHub3's.   I have a very good signal to mine. 
 It is because the router lock WPS.  I am unable to determine why at this 
point, I can get about 0.12% of the way through an attack before they lock.

I have tried the following commands on reaver 1.4 in backtrack 3

reaver -i mon0 -b 00:**:**:**:**:** -vv -c 6 -d 45 -S

reaver -i mon0 -b 00:**:**:**:**:** -vv -S -N -L -d 30 -r 3:15 -T .5 -X 360

same happens, they eventually lock out after after 30 or so pins at a rate of 
something like 7100 seconds / pin.

Some advice would be gratefully received.

Thanks

Original comment by mat.flet...@gmail.com on 29 Apr 2013 at 1:32