Stuck at the same number

[GoogleCodeExporter]

Hello guys!

Backtrack 5 r1 -->Vmware 8 -->Alfa 036h. (reaver 1.2)

First time it worked great, from 2% to 90%, i had the code 15min later.(wpa)

Now when i try wpa 2 it just stuck at the same number and goes over and over 
again, all night long.

i do this:

airmon-ng

airmon-ng start wlan0

airodump-ng mon0

reaver -i mon0 -b xxxxxxxxxx

where do i put this files? for some ppl that had worked, but i dont know where 
do i put it?

http://code.google.com/p/reaver-wps/source/detail?r=20

thanks for the help!

Original issue reported on code.google.com by An000000...@gmail.com on 3 Jan 2012 at 7:38

[GoogleCodeExporter]

What too do? please!

http://imageshack.us/photo/my-images/851/failvi.png/

Original comment by An000000...@gmail.com on 3 Jan 2012 at 1:10

[GoogleCodeExporter]

WPA vs WPA2 should not make a difference Reaver does not attack WPA. Since 
Reaver obviously worked the first time, this sounds like an AP or set up issue. 
Can you provide any output from Reaver and pcap files?

You asked where to "put this files"...what files are you talking about? Are you 
asking how to check out code from subversion?

Original comment by cheff...@tacnetsol.com on 3 Jan 2012 at 1:31

[GoogleCodeExporter]

Hello!

where do i find the output from reaver and should i upload the pcap files?

Original comment by An000000...@gmail.com on 3 Jan 2012 at 2:28

[GoogleCodeExporter]

Run Reaver with the -vv option. Output will be printed to screen. Please attach 
the pcaps to your posts here.

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

[GoogleCodeExporter]

So this might be an obvious question, but does the AP you are attacking support 
WPS?

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

[GoogleCodeExporter]

http://imageshack.us/g/849/18578936.png/ 3 pictures

i run walsh, ap is listed :/

run 1.3

Original comment by An000000...@gmail.com on 3 Jan 2012 at 7:04

[GoogleCodeExporter]

OK, so from your screenshots it appears that Reaver is working and the pin 
count is incrementing. Does it stop at the .46% and never increment afterwards? 
You will need to provide a pcap for me to diagnose further.

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

[GoogleCodeExporter]

my problem now is, its stuck but if a ctrl + c and wait for 2-3min its start 
again 1-2% then i must click on ctrl + c again and wait 2-3mins.

warning ap limitied

stuck at the same number then i click on ctrl + c and waits 2-3mins

does anyone know a command a write or something?

thanks! :)

Original comment by An000000...@gmail.com on 4 Jan 2012 at 1:59

[GoogleCodeExporter]

What is happening is the AP is locking WPS for a few minutes, then unlocking 
it, but Reaver is not properly identifying the unlocked state. This is a known 
bug in the 1.3 release, and is fixed in the latest SVN code. 

As a work around, you can specify the -L option to tell Reaver to ignore locks. 
You will get a bunch of those "warning ap limited" messages, but as soon as the 
AP unlocks WPS it will start working again.

Since your original bug seems to have been fixed, closing this issue.

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

• Changed state: Fixed

[GoogleCodeExporter]

ok what do i write? am tierd to click ctrl + c hehe.

example:

reaver -i mon0 -b 00:01:02:03:04:05 -vv -L ?

Original comment by An000000...@gmail.com on 4 Jan 2012 at 2:32

[GoogleCodeExporter]

Yes. :)

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