90.96% PROBLEM

[GoogleCodeExporter]

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.)

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

2. Is your wireless card in monitor mode (yes/no)?

3. What is the signal strength of the Access Point you are trying to crack?

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

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

6. Please describe what you think the issue is.

7. Paste the output from Reaver below.

HI,
I HAVE A PROBLEM WITH REAVER 1.4 ON SOME ROUTERS...SO IT'S START FROM 90.96% 
AND WHEN IT REACH TO 99.99% IT'S REPEAT THE LAST PIN FOREVER BUT THIS PROBLEM 
DOESN'T HAPPEN WITH SOME OTHER ROUTERS....I HOPE YOU CAN FIX THIS BUG 
SOON..THANK'S IN ADVANCE.

REGARDS.

Original issue reported on code.google.com by KMNXP...@gmail.com on 12 Nov 2013 at 3:03

[GoogleCodeExporter]

do test with bully https://github.com/bdpurcell/bully if success...

Original comment by deltomaf...@gmail.com on 12 Nov 2013 at 1:44

[GoogleCodeExporter]

UNFORTUNATELY IT'S A SAME PROBLEM..IT'S START ATTACK FORM 90.96 TO 99.99% AND 
REPEAT SAME PIN THEN FAILED TO GET WPA KEY...I HOPE THIS PROBLEM FIXED IN THE 
NEXT VERSION OF REAVER...THANK'S ANYWAY.

Original comment by KMNXP...@gmail.com on 13 Nov 2013 at 7:32

[GoogleCodeExporter]

I'm not sure, but I believe an attack decreasing could fool this protection.

Original comment by deltomaf...@gmail.com on 13 Nov 2013 at 5:14

[GoogleCodeExporter]

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:58