xenda / reaver-wps

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

(code: 0x03)-d -T -N and -A wont work #478

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 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.)
1.4
1. What operating system are you using (Linux is the only supported OS)?
Linux Backtrack 5r3
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?
-50
4. What is the manufacturer and model # of the device you are trying to
crack?
Technicolor TG582n
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b E0:1D:3B:68:7E:E8 -d 0 -A -vv -N
6. Please describe what you think the issue is.
It still sends WSC Nack even if it gets out of order packages *repeated M1 
messages*
7. Paste the output from Reaver below.
root@bt:~# reaver -i mon0 -b E0:1D:3B:68:7E:E8 -d 0 -A -vv -N

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

[+] Waiting for beacon from E0:1D:3B:68:7E:E8
[+] Switching mon0 to channel 4
[+] Associated with E0:1D:3B:68:7E:E8 (ESSID: INFINITUM643D)
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] 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
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin

Im kind of a newbie with reaver, although I have cracked lots of APs with 
aircrack although obviusly all of them had wep keys, I have tried many 
variations of the command, especially -d -T as has been suggested in other 
treads but it only changes from code 0x03 to 0x02, other than that, it still 
keeps trying for the same pin with no results I have left the attack going for 
up to 36 hours with 0.0 % progress, I believe -N doesnt work because it still 
sends WSC NACK even if it gets M1 repeatedly, it is also suggested in another 
thread to associate with aireplay which I did adding -A but as you can see, it 
still associates with the AP.

I am sorry for my bad english and for any foolishness I could have posted in my 
dissertation but as I said I am new to this and although I have read all the 
documentation there is still a lot I dont understand yet, I appreciate any help

Original issue reported on code.google.com by azanat...@gmail.com on 8 Mar 2013 at 2:07