Code (0x02) and (0x03)

[GoogleCodeExporter]

Hi,

I get these two issue, and I have no idea why. It seems to associate with no 
problem. I even tried to associate via aireplay-ng just for the sake of it, no 
avail. I did not know how to export the log, but I took a screen shot, so I 
will upload it and share the link here. Thanks for the help.

Just noticed that the scrnshot did not capture the  command, which was:
reaver -i mon0 -b XX:XX:XX:XX:XX:XX -vv

http://postimg.org/image/3u28n3muz/

And here is scrnshot no.2 with the -d command

http://postimg.org/image/t4i1jyfoh/

Original issue reported on code.google.com by spiderma...@gmail.com on 15 Oct 2013 at 10:21

[GoogleCodeExporter]

try with:
reaver -i mon0 -b XX:XX:XX:XX:XX:XX -a -S -N -vv

Original comment by deltomaf...@gmail.com on 16 Oct 2013 at 1:52

[GoogleCodeExporter]

Hi, thanks, tried it and the same......

[+] Waiting for beacon from 0C:96:BF:BD:29:D1
[+] Switching mon0 to channel 11
[+] Associated with 0C:96:BF:BD:29:D1 (ESSID: Vodafone_29D2)
[+] 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
[+] 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
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] 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
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] 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
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] 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
[+] Nothing done, nothing to save.

Original comment by spiderma...@gmail.com on 16 Oct 2013 at 3:05

[GoogleCodeExporter]

Hi,

Most times these 0x02 and 0x03 problems are related to low signal and/or 
distance form AP, interferences etc...

But I´ve had similar issue with one router even with a -40 signal , problem 
was the M1 / M2 messages not being correctly processed, as it seems its 
happening to you as well.

I solved my case by running an mdk3 attack until the router changes channel or 
reboot, after that reaver worked just fine

step 1 - mdk3 mon0 a -a xx:xx:xx:xx:xx:xx -m (leave it running for a while)

step 2  - reaver -i mon0 -b XX:XX:XX:XX:XX:XX -a -S -N -vv

Original comment by Troikaop...@gmail.com on 16 Oct 2013 at 7:02

[GoogleCodeExporter]

 Troikaop...@gmail.com

Thank you, but no good. Did nothing different than above (0x02 code). 

I also increased the Txpower to 30 dB to eliminate the possibility of weak 
signal.

Original comment by spiderma...@gmail.com on 17 Oct 2013 at 4:33

[GoogleCodeExporter]

Hi, sorry for the questions but what is your signal streght? Ensure that you 
have -60 or below. 
Also, when you run wash, is the AP listed as wps not locked?

Original comment by Troikaop...@gmail.com on 19 Oct 2013 at 11:50

[GoogleCodeExporter]

Hi, sorry for the delay. The 'wash' command was the 1st thing I did, and it 
displays WPS Locked — NO......Signal strength is 60–63.

Original comment by spiderma...@gmail.com on 24 Oct 2013 at 1:31

[GoogleCodeExporter]

Hi, sorry for the late reply, i was hoping someone more experienced could give 
you better answer. What i see wrong is that you are sending m2 message and 
receiving m1 message so the comunication between your card and the ap is not 
going well and thats why you get the error. this could be because of distance 
from ap or low signal. run airodump on that bssid and ensure RXQ is 100, plus 
the better PWR possible, to make sure is not a low signal problem i would get a 
laptop and try the attack  as close of the ap as possible... The only time this 
type of error persisted with me even when with PWR -40 i restarted the router 
with an mdk3 and afterwards reaver worked fine... You could try bigger value 
than default on the -t flag and see if you get different output.

Original comment by Troikaop...@gmail.com on 2 Nov 2013 at 5:20

[GoogleCodeExporter]

hey guys plz help this my problem : 
http://i163.photobucket.com/albums/t295/Med-El/Sf_zpsb114a7bd.png

Original comment by backn...@gmail.com on 2 Mar 2014 at 2:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I FOUND THE PROBLEM!!! = Distance!!! Basicly reaver tries the same code over 
and over because it did not receive back the signal that says the code didnt 
work so that it can try a new one that's basicly it( and of course after u did 
command - airmon-ng check kill)when i try using a reaver on a AP thats directly 
in my bros bedroom it works(appx 7 meters away) So now im looking for a 
stronger wifi adapter

Nothing is a 100% sure in this world try what i did to resolve it for me i hope 
this helps!

Original comment by calvicda...@hotmail.com on 5 Jun 2014 at 12:25

[GoogleCodeExporter]

i had the same issue and solved it with a directional antenna and the 
--no-nacks command, if the pwr is > 55 it speeds up the process and deletes the 
errors 

Original comment by karlhein...@gmail.com on 15 Dec 2014 at 3:58

[GoogleCodeExporter]

I will back the solution as being simply distance. I walked maybe 30 feet in 
one direction with my laptop toward the test router some distance away, and 
increased my speed from 60+s/key to now 4s/key. Distance is a game changer. 
Invest in a stronger card though it won't make nearly as much distance as 
finding a way to be closer to the target for a decently long duration of time. 
Cheers!

Original comment by loganped...@gmail.com on 11 Jan 2015 at 5:53