h-eibot / reaver-wps

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

WPS transaction failed (code: 0x02), re-trying last pin #457

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
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.)

latest, just downloaded

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

backtrack 5 r3

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?

linksys e2000

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

reaver -i mon0 -c 11 -b ... -vv (have also tried -mac= -n -w and -a)

6. Please describe what you think the issue is.

reaver keeps trying the 12345670 pin over and over again always giving the 
exact same error as in the title 0x02.  Will not move on.  I have read several 
articles on here all saying different solutions but none of them seem to work 
for me.  I am using an alfa AWUS036nh, if that makes any difference, a few 
people mentioned it.

7. Paste the output from Reaver below.

Sorry, cant get it out of the VM I am running.  

Original issue reported on code.google.com by HitmanMo...@gmail.com on 12 Jan 2013 at 6:08

GoogleCodeExporter commented 8 years ago
Use live CD (usb stick)& go closer to AP

Original comment by kostad...@yahoo.com on 2 Feb 2013 at 1:47

GoogleCodeExporter commented 8 years ago
I have the same issue but I'm using ubuntu and the signal strength of the AP is 
about -35
The output is : sanfoor@linux:~$ sudo reaver -i mon0 -b (my BSSID) -vv

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

[+] Waiting for beacon from (my BSSID)
[+] Switching mon0 to channel 7
[+] Associated with (My BSSID) (ESSID: my ESSID)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] 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
[+] Sending EAPOL START request
[+] 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
[+] Sending EAPOL START request
[+] 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
[+] Sending EAPOL START request
[+] 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
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 7
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin

Please help me.

Original comment by abdulra...@muslim.se on 24 Feb 2013 at 5:26

GoogleCodeExporter commented 8 years ago
i am facing the same issue and i am booting from a USB flash drive

Original comment by khoury.s...@gmail.com on 4 May 2013 at 6:28

GoogleCodeExporter commented 8 years ago
same issue, similar setup...

Original comment by julioqc47 on 25 May 2013 at 7:42

GoogleCodeExporter commented 8 years ago
I Fixed it kinda, backtrack doesnt have the proper drivers for my wireless 
card, it works for the most part but isnt compatible with reaver.  I tried 
xiaopan and reaver works perfectly with that (they have the driver specifically 
for this card).  For now Ill just use reaver on xiaopan and backtrack for 
everything else I guess.  Anyone know how to get the better driver from xiaopan 
and put it on backtrack?

Original comment by HitmanMo...@gmail.com on 26 May 2013 at 12:17