suetabby / reaver-wps

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

Error 0x04 constantly repeating without success. #349

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)
Last SVN (1.4)

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

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?
-65 (ACKS are coming)

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

It seems to be a Netgear Router

5. What is the entire command line string you are supplying to reaver?
reaver -i wlan0 -vv -b 74:31:70:18:BC:9A -c 11 -w

6. Please describe what you think the issue is.
I have no Idea.

7. Paste the output from Reaver below.

[+] Switching wlan0 to channel 11
[+] Waiting for beacon from 74:31:70:18:BC:9A
[+] Associated with 74:31:70:18:BC:9A (ESSID: glimglim)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received WSC NACK
[+] Sending WSC NACK

Hello, i have been trying reaver with some netgear router.
I get constantly a 0x04 error, and the M-Packages seems to be sended out of 
order.
I tried every possible combination, i never get a success.

I have made a tcpdump, available here: 
http://www.xup.in/dl,18777570/broken_reaver.pcap/

Could you please have a look into it and tell me what to do.
Thanks in advance

Original issue reported on code.google.com by inop...@web.de on 2 Jul 2012 at 10:40

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I have forgotten to write that i also tryed the --no-nacks function but that 
did not helped.  a try should also be attached to the pcap. 

And I'm using a Atheros Chipset (ath9).

thanks

Original comment by inop...@web.de on 2 Jul 2012 at 10:42

GoogleCodeExporter commented 9 years ago
Some new info:
if 
i run : reaver -i wlan0 -vv -b 74:31:70:18:BC:9A -c 11 --no-nacks i get 
something like this but just 0x04 errors !!!
[+] Switching wlan0 to channel 11
[+] Waiting for beacon from 74:31:70:18:BC:9A
[+] Associated with 74:31:70:18:BC:9A (ESSID: glimglim)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin

if i removing the "--no-nacks option" i get 
[+] 0.00% complete @ 2012-07-02 18:46:45 (0 seconds/pin)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] 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 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

constantly the 0x03 error. 

So whats up here, im confused

Original comment by inop...@web.de on 2 Jul 2012 at 4:47

GoogleCodeExporter commented 9 years ago
not --no-nacks, but -N

Original comment by amiros...@gmail.com on 9 Oct 2012 at 7:49

GoogleCodeExporter commented 9 years ago
so it must be like: reaver -vv -b 00:90:4C:12:AC:17 -N -i mon0

Original comment by amiros...@gmail.com on 9 Oct 2012 at 7:53