Reaver stucks at 90,90% an repeats the same PIN

[GoogleCodeExporter]

Reaver stucks at 90,90% and repeats the PIN 99985677 over and over.

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)?
Backtrack 5 R2

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?
-27

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

5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b xx:xx:xx:xx:xx:xx -v

6. Please describe what you think the issue is.
I think, reaver doesn't find the correct first half of the PIN, because it 
isn't 9998.

7. Paste the output from Reaver below.

root@bt:~# reaver -i mon0 -b xx:xx:xx:xx:xx:xx -v

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[?] Restore previous session for xx:xx:xx:xx:xx:xx? [n/Y] y

[+] Restored previous session
[+] Waiting for beacon from xx:xx:xx:xx:xx:xx

[+] Associated with xx:xx:xx:xx:xx:xx (ESSID: xxxxxxx)
[+] Trying pin 99985677

[+] Trying pin 99985677

[+] Trying pin 99985677

[+] Trying pin 99985677

[+] Trying pin 99985677
[+] Trying pin 99985677

[+] 90.90% complete @ 2012-09-02 03:52:25 (2 seconds/pin)

[+] Trying pin 99985677

[+] Trying pin 99985677

[+] Trying pin 99985677

[+] Trying pin 99985677

[+] Trying pin 99985677

[+] 90.90% complete @ 2012-09-02 03:52:42 (3 seconds/pin)

[+] Trying pin 99985677

[+] Trying pin 99985677
^C

[+] Session saved.

root@bt:~# 

Original issue reported on code.google.com by Mo.elyou...@gmail.com on 5 Sep 2012 at 7:48

[GoogleCodeExporter]

I have exactly the same problem... then I tried... sudo reaver -i mon0 -b 
AP_MAC -vv -p 9998 and now it started from there.. recovering the percentage... 
however.. I don't know if it will guess the pin... I am waiting until 100% to 
check if it works or not and if it is really a bug. BTW: Wash says it is 
vulnerable.

Original comment by DeadEvil...@gmail.com on 7 Sep 2012 at 4:04

[GoogleCodeExporter]

DeadEvil:  Perfect.  Worked like a charm.  Now to hope it finds it within the 
last 9.1%

Original comment by Matt.Sve...@gmail.com on 9 Sep 2012 at 7:53

[GoogleCodeExporter]

Doesn't work for me, because 9998 isn't the correct first half of the PIN (it's 
my router, so I know it).

I think, 9998 it's the latest first half to test, because 9999 it's tested at 
start.
But, I don't know why reaver doesn't find the correct first half.
And that's the problem: When reaver tests the correct first half, doesn't alert 
about it. So it's like the half PIN passed, isn't correct...

I still didn't solved it :( If someone can give us some tip, I'll appreciate it.

Original comment by Mo.elyou...@gmail.com on 10 Sep 2012 at 7:19

[GoogleCodeExporter]

I'm getting this too.

Original comment by elld...@gmail.com on 14 Sep 2012 at 5:41

[GoogleCodeExporter]

I keep getting this when running reaver on my Wifi pineapple. Sticks at 90.90%. 
Have only been able to try this on one AP though so not sure if it does it for 
all. 

Currently trying the solution above, resuming it from -p 9998, though not sure 
if it needs the rest of the capture file from the previous session in order to 
retrieve the key...

Original comment by velkrosm...@gmail.com on 21 Jan 2013 at 2:49

[GoogleCodeExporter]

ty u so much it worked for me now iam able to contunue 

Original comment by lougs...@gmail.com on 23 Feb 2013 at 11:53

[GoogleCodeExporter]

It might continue, but the odds are great that it failed to use the correct pin 
preceding ones it tries after -p 9998.

I had this happen to reaver with two APs. What fixed it for me was deleting .db 
and .wpc files in /usr/local/etc/reaver and starting over.
Both APs reaver was having problems with ended up using the first pin it tries 
- 12345670.

Original comment by zivkovic...@gmail.com on 16 Apr 2013 at 7:26

[GoogleCodeExporter]

DeadEvil: you are genius!!! Thanks

Original comment by zdendas...@gmail.com on 6 Sep 2013 at 12:56

[GoogleCodeExporter]

Ran reaver for about 3 days on an AP and eventually got stuck at 99985678. I 
followed zivkovic's suggestion forcing reaver to start from the beginning, and 
surprisingly on the second run it immediately found the PIN to be 12345670 
(exactly like zivkovic reported). It also gave me the passkey, which _is_ 
indeed valid.

Original comment by fardel...@gmail.com on 2 Feb 2014 at 8:47

[GoogleCodeExporter]

Fardel, I'm having the same problem. When you got stuck at 99985678, did you 
delete the .db and .wpc files, start all over without having to save where you 
left off and without having to specify the pins?

Original comment by kyleay...@gmail.com on 8 Feb 2014 at 3:00

[GoogleCodeExporter]

SQSQS

Original comment by abdowi...@gmail.com on 12 Feb 2014 at 12:33

[GoogleCodeExporter]

Anyone ever have an issue where reaver thinks it found the first four correct 
pins and jumps to the "90%" done phase but never gets anything higher than an 
M4 packet?

It's almost like it gets a false positive on those first 4 numbers or something.

Am I going crazy or does this happen?

Original comment by psychede...@gmail.com on 27 Aug 2014 at 1:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hello eveybody. I had the same problem. I reverted back to backtrack 5 and the 
problem was solved. so I think the problem is in kali linux itself.
The command I wrote was : 

reaver -i mon0 -c 1 -A -b XXXXXXXXXXXXXXX -vv -N -w -t 5 -L -x -d 0 -r 5:3 -S 
-p 9998

in another terminal I used aireplay : 

aireplay-ng mon0 -1 120 -a XXXXXXXXXXXXXXX -e XXXXXXXXXxx -q 5

The pin continued. This is a 100 % working.
 Ciao from Morocco. By K.Abdelilah

Original comment by khabchit...@gmail.com on 27 Sep 2014 at 10:50

[GoogleCodeExporter]

Upgrade to reaver 1.5 and then start it by reaver -I mon0 -b (what ever) -c 
(what ever channel) -1 9998 -vv

Original comment by strife7...@gmail.com on 5 Oct 2014 at 12:44