satwinde / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

99.99% v1.4 #504

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

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.)
Reaver Version 1.4

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

2. Is your wireless card in monitor mode (yes/no)?
Yes - Its an ALFA AWUS036NHR

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

4. What is the manufacturer and model # of the device you are trying to
crack?
D-Link DSL-2780  from TalkTalk

5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -c 1 -b AA:AA:AA:AA:AA:AA  -vv

6. Please describe what you think the issue is:

Gets stuck at 99.99% repeats trying the same PIN. 
I have not been WPA locked.(Checked with wash)
I know this issue has been raised before but i believe it was to have been 
solved in version 1.4 hence the post.

7. Paste the output from Reaver below.

[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[+] Trying pin 12349982
[+] 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
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[+] Trying pin 12349982
[+] 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 M5 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] 99.99% complete @ 2013-05-10 09:46:50 (2 seconds/pin)
[+] Trying pin 12349982
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response

Original issue reported on code.google.com by sinkingt...@gmail.com on 10 May 2013 at 9:03