Stuck on same PIN after one minute

[GoogleCodeExporter]

>What steps will reproduce the problem?
Normal usage to an AP 1M away from my adaptor

>What is the expected output? What do you see instead?

Expected o/p is rorating PIN Until successful completion. What I see is the PIN 
will change for about 1 minute and then get stuck on the same PIN.AP is a 
Netgear WNR2200

>What version of the product are you using? On what operating system?

--reaver 1.2 (no SVN updates)
--Ubuntu 11.10 64-bit
--Alpha AWUS036H USB adaptor

>Please provide any additional information below.

pcap file attached.I was getting the segmentation fault but this has 
dissapeared.THis may be a localised AP issue as on other AP's with very good 
RSSI, I dont get the "stuck" PIN but what I do get are/is very frequent 
timeouts.I will raise this on a seperate ticket?

Great tool, BTW.I'm a bot of a noob when it comes to LInux but very interested 
in wireless.Anything else you need, just let me know.

Original issue reported on code.google.com by stew.d...@gmail.com on 31 Dec 2011 at 8:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Sorry-my system is a 32-BIT system

Original comment by stew.d...@gmail.com on 31 Dec 2011 at 11:32

[GoogleCodeExporter]

A timeout just means that Reaver didn't get the expected next packet within the 
allotted amount of time; this could be due to corrupted or dropped packets on 
either the attacker's or the AP's side. You typically see this a lot if you 
have a lot of APs/interference in your area, or if the target AP has a low 
signal strength.

The Netgears usually do implement lock-outs, so this could be the issue, 
although Reaver will usually warn you when it detects that the AP has locked 
itself.

I'm going to be out of town for the holiday weekend, I'll take a closer look at 
the pcap when I get back. Thanks!

Original comment by cheff...@tacnetsol.com on 31 Dec 2011 at 1:29

[GoogleCodeExporter]

@stew, I added these options, when starting reaver, "-r 20:30 -d 3"  since I 
was getting lock-out/rate-limit/same pin issues after about two-to-three 
minutes with my WNR1000, WNDR3400, and WNDR4000 routers.

Original comment by juanpedr...@gmail.com on 31 Dec 2011 at 2:24

[GoogleCodeExporter]

stew, taking a look at the pcap it doesn't look like the typical MO of a 
lockout, but different vendors and devices implement WPS slightly differently 
sometimes so this could be the issue. It looks like your pcap stops about 1.5 
minutes after you started getting the errors; did you try letting it run 
longer, or stopping, waiting and re-starting the attack?

Original comment by cheff...@tacnetsol.com on 3 Jan 2012 at 4:18

[GoogleCodeExporter]

stew, have you tried specifying the --win7 option? Some APs are particular 
about their M2 WPS messages, which is where your pin attempts are failing.

Original comment by cheff...@tacnetsol.com on 3 Jan 2012 at 6:49

[GoogleCodeExporter]

Hi guys,
Finally got it working using BTR1, on Vmware 3.1.5 player. Used 1.3 beta. Alpha 
USB card as previously described. Options were

reaver -i mon0 -b xx.xx.xx.xx.xx -d 0 -t 10 -w -vv

Hope this helps others-seems to be VERY AP dependent as others I can associate 
but no PIN generations, others I cant even associate. Power levels are good.

Original comment by stew.d...@gmail.com on 3 Jan 2012 at 7:30

[GoogleCodeExporter]

Yup, some APs are very particular, which is why there are all those advanced 
options in Reaver. :P  This is also why there's the --auto feature and the 
database for plugging in options to be used automatically whenever XYZ router 
is encountered.

Original comment by cheff...@tacnetsol.com on 3 Jan 2012 at 7:38

• Changed state: WontFix

[GoogleCodeExporter]

Just got the latest from SVN, which I take it has the newly released full blown 
version. Is there a part/FAQ that tells you how to use the web side of the tool?

Original comment by stew.d...@gmail.com on 3 Jan 2012 at 8:03

[GoogleCodeExporter]

The command line version of Reaver has been fully open sourced. The GUI front 
end is still only for the commercial version. See issue #54.

Original comment by cheff...@tacnetsol.com on 3 Jan 2012 at 9:00

[GoogleCodeExporter]

i have the same problems, i get % BUT! i must turn it off for 3min and then 
start it again, and do this all the time. it allways stuck after 1-2%

backtrack 5 vmware alfa 036

anyone know what too do? :(

Original comment by An000000...@gmail.com on 4 Jan 2012 at 9:23

[GoogleCodeExporter]

if i dont  press ctrl c its just stuck on the same pin and trying and trying 
all the time, but when i press ctrl c and waits 3-4min its works fine 1-2%

Original comment by An000000...@gmail.com on 4 Jan 2012 at 9:30