danhnh / reaver-wps

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

m2 timeout / 0x02 or 0x03 error/ only "received m1 message" #639

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 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.)

reaver 1.4

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

wifislax 4.8 (but 4.6 gives the same problem)

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?

rssi: -35

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

alfa awus036h

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

reaver -i mon0 -b 4C:54:99:xx:xx:xx -a -c 6 -e "xxxx" -N -S -vv

6. Please describe what you think the issue is.

I don't know why with these options i only get to:

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 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
WARNING: Receive timeout occurred
Sending WSC NACK
WPS transaction failed (code: 0x02), re-trying last pin

what am i doing wrong?

Original issue reported on code.google.com by sto...@hotmail.it on 3 May 2014 at 9:40

GoogleCodeExporter commented 9 years ago
try add -w  and or remove -N
reaver -i mon0 -b 4C:54:99:xx:xx:xx -a -c 6 -N -S -vv -w

Original comment by deltomaf...@gmail.com on 3 May 2014 at 9:04

GoogleCodeExporter commented 9 years ago
like this:

reaver -i mon0 -b 4C:54:99:xx:xx:xx -a -c 6 -S -vv -w

i get:

Trying pin 12345670
Sending EAPOL START request
Received identity request
Sending identity response
Received M1 message
Sending M2 message
Received M1 message
Sending WSC NACK
Sending WSC NACK
WPS transaction failed (code: 0x03), 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
Sending WSC NACK
Sending WSC NACK
WPS transaction failed (code: 0x03), re-trying last pin

why the double "Sending WSC NACK"? Any suggestions?

Original comment by sto...@hotmail.it on 16 May 2014 at 6:59

GoogleCodeExporter commented 9 years ago
I've had this problem a couple of times, I found two different solutions for 
each

1- as delto suggested use the -w option

2- reboot the AP with an mdk3 attack and then use the -w option

If you try bully and it give you some "out of sync" warnings, definitely try to 
reboot the AP

Original comment by Troikaop...@gmail.com on 10 Jun 2014 at 2:34

GoogleCodeExporter commented 9 years ago
guys , pleaseee help me :(((
i install bully and do commands right !
but i get this ! :

root@Max:~# bully -b xx:xx:xx:xx:xx:xx -c 6 -T  mon0
[!] Bully v1.0-22 - WPS vulnerability assessment utility
[+] Switching interface 'mon0' to channel '6'
[!] Using '00:11:22:33:44:55' for the source MAC address
[+] Datalink type set to '127', radiotap headers present
[+] Scanning for beacon from '60:a4:4c:ee:cd:a4' on channel '6'
[!] Excessive (3) FCS failures while reading next packet
[!] Excessive (3) FCS failures while reading next packet
[!] Excessive (3) FCS failures while reading next packet
[!] Disabling FCS validation (assuming --nofcs)
[+] Got beacon for 'milk' (xx:xx:xx:xx:xx:xx)
[X] The AP doesn't appear to be WPS enabled (no WPS IE)

Help me :(

Original comment by pooya.si...@gmail.com on 29 Sep 2014 at 4:59

GoogleCodeExporter commented 9 years ago
what does your error has to do with the one that was posted??
seriously?

Original comment by sto...@hotmail.it on 30 Sep 2014 at 8:36