Open GoogleCodeExporter opened 8 years ago
[deleted comment]
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
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
not --no-nacks, but -N
Original comment by amiros...@gmail.com
on 9 Oct 2012 at 7:49
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
Original issue reported on code.google.com by
inop...@web.de
on 2 Jul 2012 at 10:40