Blocks me at 90,90%

[GoogleCodeExporter]

0. Last version from svn 1.4 v107

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

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?
-50/-60

4. What is the manufacturer and model # of the device you are trying to
crack?
wlan0       Intel 4965AGN   iwl4965 - [phy0]
                (monitor mode enabled on mon1)
mon0        Intel 4965AGN   iwl4965 - [phy0]

5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 00:24:17:73:DD:3D -E -L -t 5

6. Please describe what you think the issue is.
it blocks me at 90,90%

7. Paste the output from Reaver below.
...
[+] 90.90% complete @ 2012-01-21 03:35:41 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:36:09 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:36:48 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:37:11 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:37:41 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:38:18 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:38:56 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:39:19 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:39:49 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:40:15 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:40:42 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:41:06 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:41:31 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:41:59 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:42:23 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:42:48 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:43:13 (7 seconds/pin)
[+] 90.90% complete @ 2012-01-21 03:43:42 (7 seconds/pin)
...

Original issue reported on code.google.com by poiert2...@gmail.com on 21 Jan 2012 at 3:37

[GoogleCodeExporter]

I notice you are using the -L option. If you don't specify this option do you 
get the 'detected AP rate limiting' message?

Original comment by cheff...@tacnetsol.com on 21 Jan 2012 at 6:02

[GoogleCodeExporter]

Can you run the command with -vv for more verbose output?

I had the same problem with an AP where it got stuck at 90.90%
Reaver kept trying the exact same PIN over and over.

Original comment by alibo...@gmail.com on 22 Jan 2012 at 2:39

[GoogleCodeExporter]

I also stopped at 90.90%, and tries again and again the same pin
I do not know what to do, I want to get help

Original comment by uniz...@aol.ru on 22 Jan 2012 at 4:03

[GoogleCodeExporter]

Check this topic: http://code.google.com/p/reaver-wps/issues/detail?id=83

Supposedly this issue has been fixed in the latest source in svn.

Original comment by alibo...@gmail.com on 22 Jan 2012 at 4:20

[GoogleCodeExporter]

unizzon, first make sure you are running the latest SVN code. This was a bug 
that has previously been found and fixed. Basically the output you are getting 
indicates that reaver has attempted all of the possible combinations for the 
first half of the pin but still hasn't found the right one.

However, it has been found that some APs will always report that the first half 
of the pin is incorrect (even if it is the right one!) if the AP is in a locked 
state. So if you tell reaver to ignore lock outs (-L / --ignore-locks) you can 
miss the pin altogether. This is why I asked poiert what happens if he does not 
supply the -L option.

Original comment by cheff...@tacnetsol.com on 22 Jan 2012 at 6:33

[GoogleCodeExporter]

i will try again without the -L flag, come back later to say if works

Original comment by poiert2...@gmail.com on 22 Jan 2012 at 7:40

[GoogleCodeExporter]

Hi Craig, I do not use the option - L
2 hours ago made a revision here 
http://code.google.com/p/reaver-wps/source/checkout
seems to be written that 109, if not forgotten, and I'm not mistaken.
as a result, all that was before http://www.bild.me/bild.php?file=24880541.png
AP previous two weeks was given properly without such hang-ups, and even with a 
jump from 60% to 90%.
I will wait to resolve the situation in the future.
thank you

Original comment by uniz...@aol.ru on 22 Jan 2012 at 8:05

[GoogleCodeExporter]

unizzon, you are going to have to start the attack again, restoring the 
previous bad session won't help.

"AP previous two weeks was given properly without such hang-ups, and even with 
a jump from 60% to 90%."

Are you saying that Reaver worked on other APs 2 weeks ago, or that you tested 
the same AP (74:EA:3A:A9:6A:90) 2 weeks ago and it worked then?

Original comment by cheff...@tacnetsol.com on 23 Jan 2012 at 12:19

[GoogleCodeExporter]

Hi,
I've the same problem, just one input, if I try without ignoring locks, I get 5 
minutes AP rating detection systematically, such that it does 60 seconds/pin. 
This could turn the attack into days

Original comment by tiago.ju...@gmail.com on 23 Jan 2012 at 1:39

[GoogleCodeExporter]

taigo, there's not much Reaver can do about that. If the AP continues to 
respond to WPS pin attempts while "locked", but you never get the right pin and 
end up getting stuck at 90.9%, then the AP is probably giving you false 
negative reports while it is locked and you'll have to honor the locking 
period. Yes, this can make the attack last days, but to put it in perspective a 
few days to break a WPA key is nothing.

Original comment by cheff...@tacnetsol.com on 23 Jan 2012 at 1:54

[GoogleCodeExporter]

Cheff, I mean another AP, this is not

Original comment by uniz...@aol.ru on 23 Jan 2012 at 7:00

[GoogleCodeExporter]

i have same problem check image file

http://www.fmsecond.com/di-LNS2.png

Original comment by virusran...@gmail.com on 23 Jan 2012 at 7:46

[GoogleCodeExporter]

It's easy to test if this is the AP returning false negative reports or not:

1) Reboot the AP to ensure a fresh start.
2) Run Reaver with the --pin option, specifying the correct WPS pin for the 
target AP to make sure the correct pin works.
3) Run Reaver without --pin, without -L and with -vv and do not restore any 
previous sessions.
4) Wait until you start getting "rate limiting detected" warnings.
5) Immediately stop reaver and re-run #2, but this time with the -L option. 
Does the correct pin still work or not?

Original comment by cheff...@tacnetsol.com on 23 Jan 2012 at 2:23

[GoogleCodeExporter]

I had this problem, ran without the -L switch and NOW reaver correctly found 
the key :) nice

Original comment by kub...@gmail.com on 25 Jan 2012 at 12:29

[GoogleCodeExporter]

Thanks Cheff, without the -L the key was properly found. yeh

Original comment by tiago.ju...@gmail.com on 28 Jan 2012 at 5:50

[GoogleCodeExporter]

Thanks Cheff, reaver 1.4, attack again, all ok, the correct key is found

Original comment by uniz...@aol.ru on 3 Feb 2012 at 2:12

[GoogleCodeExporter]

hi, im kind of new to this cheff, but i have this proble with reaver 1.4 
repeating pin at 90.90% . i am not using the -L option or anything other than 
-vv. i am also experiences reaver crashing many times and having to restart 
from sratch. can you please help me??? thanks 

Original comment by slaughta...@gmail.com on 6 Feb 2012 at 1:25

[GoogleCodeExporter]

Same problem here:( iv tried everything mentioned here.

Im using latest trunk 112, iv tried with out without every command. It stalls @ 
90,90% and i cant get it to continue. 
Using it close to my router so that isnt it.

Please help

Original comment by frederi...@gmail.com on 9 Mar 2012 at 10:20

[GoogleCodeExporter]

I'm also stonewalled at 90.90% and I never used the -L switch. Any suggestions?

Original comment by shoredit...@gmail.com on 18 Mar 2012 at 3:02

[GoogleCodeExporter]

same here using rev 113!

Original comment by livewin...@gmail.com on 28 Mar 2012 at 11:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have the same problem at 90.9%.
Reaver is trying the same pin over and over.
I'm very noob, i have to say, but i don't use the option (--ignore-lock)

I use:
reaver -i mon0 -E -L -T 5 -c 1 -b 00:xx:xx:xx:xx:xx -vv
or 

reaver -i mon0 -E -L -T 2 -c 1 -b 00:xx:xx:xx:xx:xx -vv

If i don't use the -L option reaver show very "WARNING: Detected AP rate 
limiting, waiting 60 seconds before re-checking"

root@bt:~/reaver/src# reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv

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

[?] Restore previous session for 00:26:44:97:4E:65? [n/Y] n
[+] Waiting for beacon from 00:26:44:97:4E:65
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 5
[+] Switching mon0 to channel 6
[+] Switching mon0 to channel 7
[+] Switching mon0 to channel 8
[+] Switching mon0 to channel 9
[+] Switching mon0 to channel 11
[+] Associated with 00:26:44:97:4E:65 (ESSID: xxx)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00005678
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 01235678
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 11115670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 22225672
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking
[!] WARNING: Detected AP rate limiting, waiting 60 seconds before re-checking

And took one night to make 2,2%.
at this speed it could take a month to reach to 100%.
i use rev 113, alfa aWuso36H in VMware

i have run the command "svn checkout 
http://reaver-wps.googlecode.com/svn/trunk/ reaver"
and the "./configure && make && make install"

what sould i do cheff...@tacnetsol.com ?

Original comment by ricardoj...@hotmail.com on 6 Apr 2012 at 4:55

[GoogleCodeExporter]

I am booting backtrack 5r2 from the cd-rom and i got the "request timed out" on 
2 different APs after running reaver for a while. the first one stuck at 10% 
and the second at 20%
I am simply using reaver -i mon0 -b bssid -vv
i tried adding the --no-nacks argument as well as the -d up to 30 and neither 
worked. any advice? 

Original comment by pacoo...@abv.bg on 10 Apr 2012 at 4:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Same here, on BT5R2 and reaver rev 113, stuck at 90.90%  with the 99985677 pin 
on "reaver -i .... -b ..... -v" and RTL8187 chipset. 
It try the same pin again & again even when I do "-p 99958677" or around.

I've modified the .wps in /usr/local/etc/reaver to force the pin, but nothing 
worked.

Let me now if I can help.

Original comment by arnaud.f...@gmail.com on 4 May 2012 at 4:10

[GoogleCodeExporter]

Arnaud, did you recompile and install the program? Just changing the .wps files 
won't do any good. Also, I have tried rev 112 and 113 on reaver 1.4 to no 
avail, I keep getting the same issue... 90.90%. I know this issue has 
supposedly been fixed, but here we are.

BT5R2 Installed to HD
Alfa AWUS036H w/ RTL8187

any ideas? I have tested reaver on other APs and it has been successful.

Original comment by gibp...@gmail.com on 26 May 2012 at 5:05

[GoogleCodeExporter]

Yes, I've recompile reaver and re-install it on BT5R2, on 3 different PC,  and 
also try it on ubuntu 12.04 and nothing changes, both on 1.3 and last rev of 
1.4.
I don't think it's reaver problem, because  you say that it work on other AP, 
and because the 90.90% seems to be the last bruteforce try of the first part of 
pin ("9998"), and the first try of the second part of pin.
So, I think reaver doesn't receive correctly the answer of AP that says the 
first part of pin tried is the good one.

I hope it helped!

Original comment by arnaud.f...@gmail.com on 26 May 2012 at 10:39

[GoogleCodeExporter]

It must be a bug, everyone crashes on that number at that percentage% and 
certainly that pin isnt the same for all. Not event the beggening part.

Original comment by frederi...@gmail.com on 13 Jun 2012 at 1:52

[GoogleCodeExporter]

Hi. im having exactly same issue. i'm not on my linux OS atm, so i can't post 
the exact log.
command im using is this
reaver -i mon0 -b xx:xx:xx:xx:xx:xx -vv -S -w -E -d 29 -x 11

this was original command, but later i removed -w and -E, could those be the 
problem causers ?
never used -L option.
also if i set -d to 28 or below, AP will lock WPS for 3-4 minutes. that happend 
few times when i was testing, however i did not ignore locks, so i waited until 
WPS was unlocked and continued the attack.

Now its stuck at 90.20% and keeps trying same pin 99985677 (i think end was 
5677).

I also noticed there is no 9999, so i changed 9998 to 9999, but no difference. 
except that it showed 90.90% and 99995677, but no progress.

What should i do ?

Card im using is by TP-LINK with some atheros chipset. supports monitor mode, 
able to crack WEP networks..etc

Original comment by mordax on 28 Jul 2012 at 3:04

[GoogleCodeExporter]

Same issue here.
It's stuck at 90.90% and keeps trying pin 99985677 over & over.

I'm using this command:
reaver -i mon0 -b xx:xx:xx:xx:xx:xx -c 4 -v

I hope someone can give us a solution. Thank you.

[I've tried with reaver 1.3, 1.4 R96, etc. and it's stuck at the same % and 
same pin. Also I've tried with this command "reaver -i mon0 -b 
xx:xx:xx:xx:xx:xx -c 4 -p 9998 -v"]

Original comment by Mo.elyou...@gmail.com on 2 Sep 2012 at 6:43

[GoogleCodeExporter]

Totally the same #34 comment issue:
* 90.90%
* pin number 99985677

Some log:

[+] 90.90% complete @ 2012-09-08 23:21:41 (2 seconds/pin)
[+] Trying pin 99985677
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 99985677
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 99985677
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 99985677
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK

This is the second attempt that stucks at 90.90%.
I tried to force it with -p 9998. Then, reaver reaches 99.99% and get stucked 
waiting for Maya coming, I guess :)
Any fix?
Thanks

Original comment by imorgi...@gmail.com on 8 Sep 2012 at 9:27

[GoogleCodeExporter]

I am also having the same problem of 90.90% looping at 99985677 on a Dell 
(1450?) Network card. 
Used:  reaver -i mon0 -b MAC --dh-small -vv --delay=0 --recurring-delay=30:15 
--no-nacks

Works beautifully (?) at this point until it reaches 9985677; then it just 
keeps looping. Changing to -pin equals 99985678 does not seem to help. AP is a 
Belkin.Using BK5r3 and 1.4 Reaver. Been able to crack several other APs without 
any unusual problems; some very quickly. 

Works beautifully (?) at this point until it reaches 9985677; then it just 
keeps looping. Changing to -pin equals 99985678 does not seem to help. AP is a 
Belkin router. My laptop using BK5r3 and 1.4 Reaver. Dell network card 1450 
(?); been able to crack several other APs without any unusual problems; some 
very quickly. I've tried all the channel IWCONFIG and AIREPLAY-NG suggestions 
on numerous threads but nothing fixes.

Original comment by chris.t....@gmail.com on 29 Nov 2012 at 3:37

[GoogleCodeExporter]

same issue here

Original comment by Trimbita...@gmail.com on 1 Dec 2012 at 7:05

[GoogleCodeExporter]

I have the exact same issue. Ive gone through all the 10k numbers, have not 
used the -L parameter.
60secs a key, took me forever - and now it wont continue.
When will this be fixed?

Original comment by orjan.tr...@gmail.com on 19 Dec 2012 at 8:54

[GoogleCodeExporter]

For all those getting this issue. I have tried to solve it and I found that it 
wasn't a problem with the reaver. It is an AP configuration issue.

This happens:

1- If you put into the PIN code of the configuration a bad string (letetrs 
instead of number, for example).

2- When you disable the WPS via the web based interface of the AP and don't 
reboot. Sometimes happens when you reboot too.

I hope this helped ;)

Original comment by Mo.elyou...@gmail.com on 22 Dec 2012 at 9:07

[GoogleCodeExporter]

Same issue here, reaver 1.4 + BTR3, stuck at 90.9% / PIN: 99985677. I was using 
the -L flag, re-running the attack without the flag to see if it has any impact.

Using this command:
reaver -i mon0 -b XX:XX:XX:XX:XX:XX -vv -S -N -L -d 1 -r 40:15 -T 1 -t 10 <- 
stuck at 90.9%.

Now I'm, retrying the same AP with:
reaver -i mon0 -b XX:XX:XX:XX:XX:XX -vv -S -N -d 1 -r 40:15 -T 1 -t 10 <- same 
as above just no -L flag.

Reaver is running now with the new command, I will report back in a few hours 
when it finishes or gets back to 90.9%! :)

Original comment by dwasy...@gmail.com on 9 Jan 2013 at 5:11

[GoogleCodeExporter]

How did you get on with this? I'm trying various options too...

Original comment by velkrosm...@gmail.com on 22 Jan 2013 at 1:02

[GoogleCodeExporter]

try reaver -i mon0 -b AP_MAC -vv -p 9998 and now it should start from there.. 
you lose a few keys in the process but at least it bypasses the loop... i do 
not know if this will recover a key i am currently testing this! at least i 
aint stuck at 90.9% anymore

Original comment by phyra...@gmail.com on 24 Feb 2013 at 6:30

[GoogleCodeExporter]

Same Prob. here!!!! I see everybody is having the same problem!!! Does anybody 
actually found a solution?! and did anybody notice that the second half of the 
pin doesn't change "xxxx567x" i mean the 4first half reaver change the nimbers 
but the socond half change just the last number!!! and it seems to me that it 
is the same for everyone so does anybody knows why?! It can't be a correct half 
for all of us!!! nad why just those numbers "567"?

Original comment by paquin...@gmail.com on 4 Mar 2013 at 12:36

[GoogleCodeExporter]

paquin - That sounds like a slightly different problem than the one here.

I'm having this issue, stuck at 90.9% and pin 99985677 on two different APs. 

Regarding dwasy's note about -L: I didn't use -L (I tried various other 
combinations, sometime including auto -a, but never -L), and sometimes I used 
no options at all (just -vv) and got stuck at the same place every time. 

I also tried phya's suggestion of -p 9998 but that didn't change my output at 
all, still stuck on the same spot.

As to Mo.elyou, what's the likelihood that all of us are getting stuck at the 
exact same percent and even the exact same pin (99985677), and in some cases on 
multiple APs per person, if this is not actually reaver's fault, but an AP 
config problem? Not a chance - definitely has to be a reaver bug.

For general purposes, let me say I'm running reaver 1.4, and I successfully 
cracked 1 AP with it last fall (though I'm not sure what version I was running 
at the time, sorry). But now with my new router and my neighbors' I'm getting 
stuck at this same pin every time, no matter what options I use, no matter how 
fast or slow it works, and no matter if I do a fresh clean boot of backtrack 
live and an updated install of reaver or not.

Is anyone out there working on this? I'm a coder and would like to help 
contribute to any ongoing efforts.

Original comment by vanessa....@vanderbilt.edu on 4 Mar 2013 at 10:07

[GoogleCodeExporter]

Hi Vanessa, Sorry I think I did not explain myself properly so there:
 I AM TALKING ABOUT YOUR EXACT SAME ISSUE I GOT STUCK @ 90.90% and reaver still trying the same pin: "99985677" 
+ What I am saying is that:
 I HAVE NOTICED THAT THE SECOND HALF OF THE PIN DOES NOT CHANGE FROM: "xxxx567x" (567) STARTING FROM 0% UP TO 90.90% reaver tried all the possible combinations from "00005670 to 99985679" but the "567" never changed throught all the process and combinations and I am also sure that it is a reaver bug the fact that it stuck @ 90.90%.
Did anybodyelse noticed that that: "567" never actually change I guess It would 
change only if Reaver sucessfully Crack the first half!!!! 
I am trying to understand why It did not change that part of the pin as I think 
this is also associated with the SAME BUG. 
I also have tried all possible combinations and It did take days to get up to 
90.90% and then it got stuck to 99985677 @ 90.90%; @ this point I did try the 
option: "-p 99997869" resuming my last session and i noticed that the 
percentage started increasing but the pin did not changed the one I've inputed, 
Still trying though!
Now I did also try the option "-p ********" Suggesting the ACTUAL PIN of the 
router I am testing and i did obviously find it was the right one and so 
succesfully CRACK the PIN.
Now I started a fresh attempt on the router just cracked. From 0% with the very 
basic command of Reaver (reaver -i xxxxx -b xx:xx:xx:xx:xx -vv) to see how it 
goes this time when it will reach the first half of the pin (@ 50.00% should be 
done)+ I want to see if it does stop @ that point attempting that half and so 
start changing the second half as it is not: "567x" and than I am hoping Reaver 
will try differt pin other than: "567x". 

Just for general info:  
I was alvays using: Reaver-1.4
Since I started, till this morning I did use BackTrack5-R1 with not success 
what so ever getting stuck @ 90.90% with Reaver repeating pin: 99985677;
Today I started a fresh attack with also Reaver-1.4 but this time I am using 
BackTrack5-R3 and trying different router here @ home plus also one of my 
neighbor.

I can definitely say that Reaver On BT5-R3 is faster than in older versions of 
BT!!!

Will lett you know how It goes this time as I am also trying to read as much 
forums and info about this same problem and there are so many forums and 
discussions about this issue with people reporting the same but I am yet to 
find someone that has actually work out a solution!!!  

Original comment by paquin...@gmail.com on 5 Mar 2013 at 2:00

[GoogleCodeExporter]

ok Here My Update on the issue:
(Most probably you already know all I am going to write down but as no one has 
posted it so far I am going to):
Reaver it begin to crack the first 4Digits of the WPA pin number, then from 
there it will crack the second 4Digits. 
If the first part of the pin doesn't get to be cracked reaver will not crack 
the second part!!! 
When reaver stuck on loop on 90.90% trying the pin "99985679"over & over It is 
because reaver already tried all the possible combinations for the first 
4Digits and It has not more to try: Obviously: It did not work!!! 
Now I am not quite sure yet, if, this is the case when reaver cannot crack the 
pin what so ever for that router WPA I am still testing: I am trying for the 
3th time to crack the pin on the router I am testing and having this issue! 
So I will let you know soon I guess! lol
Please people post and share your experiences and results: They are very 
usefull for all of us!!! Everything is apreciated!!!
Now Does anybody have tried more than one time to test the same router that was 
giving the above issue and manage to get succesfull results on the second or 
third time?! 
PS.:I do apologize for my english and if I may not be clear. Please be kind and 
fell free to ask me for explanations and clarifications!!!
Thank you all!!!

Original comment by paquin...@gmail.com on 9 Mar 2013 at 12:56

[GoogleCodeExporter]

Update: I succesfully cracked 3 different router I was testing and having the 
above issue on a 4th one + having more different issues on a fifth and sxth 
one!!! In some cases I cannot manage to get it started @ all as it stuck @ 
0.00% and I can say it is not working in that case as it seems to me that 
Reaver is basically having difficulties to start the cracking process!!!! Still 
trying though!!!
One more thing: I also noticed that: If I start 2 different reaver process, 
even using 2 different interfaces(wireless cards) Reaver doesn't seems to work 
properly!!!
If I want Reaver to work properly I need to start Reaver with just one process 
and then wait and leave the computer alone & do nothing @ all till Reaver has 
finished this is the only time I did manage to get Reaver to work succesfully!!!

Original comment by paquin...@gmail.com on 9 Mar 2013 at 1:09

[GoogleCodeExporter]

Oh Finally something concrete!!!

Thanks Paquin will let you know how I am getting on soon!!!

I am tesing my other routher but it is taking lot of time!!! 
So I dunno what to do or what to expect. 
I guess I should just sit and watch!!!! 
I am just so impatient to see some results!!!

Original comment by david...@gmail.com on 9 Mar 2013 at 1:17

[GoogleCodeExporter]

stay blocked for a long time at 0% I don't know what the problem if you can 
help me help me please?

Original comment by zakibadi...@gmail.com on 18 Mar 2013 at 6:09

[GoogleCodeExporter]

i have same issue. i try 2 different AP.

reaver 1.3 and 1.4.. not working stable... Always stuck %90.90

Original comment by s.wra...@gmail.com on 11 Apr 2013 at 10:01