search

shunz1 / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

reaver operating too slow. #355

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 

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

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

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?
around 60
4. What is the manufacturer and model # of the device you are trying to
crack?
don't know.
5. What is the entire command line string you are supplying to reaver?
i've tried different commands but at least it was:
reaver -i mon0 -b 14:D6:4D:B5:71:00 --no-nacks -c 6
6. Please describe what you think the issue is.
a wrong command maybe
7. Paste the output from Reaver below.
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[?] Restore previous session for 14:D6:4D:B5:71:00? [n/Y] n
[+] Waiting for beacon from 14:D6:4D:B5:71:00
[+] Associated with 14:D6:4D:B5:71:00 (ESSID: sara)
[+] 0.01% complete @ 2012-07-14 06:43:13 (77 seconds/pin)
[+] 0.02% complete @ 2012-07-14 06:44:10 (67 seconds/pin)
[+] 0.05% complete @ 2012-07-14 06:45:01 (37 seconds/pin)
[+] 0.07% complete @ 2012-07-14 06:46:11 (31 seconds/pin)
[+] 0.08% complete @ 2012-07-14 06:47:13 (35 seconds/pin)
[+] 0.09% complete @ 2012-07-14 06:48:24 (38 seconds/pin)
[+] 0.12% complete @ 2012-07-14 06:49:22 (34 seconds/pin)
[+] 0.13% complete @ 2012-07-14 06:50:16 (35 seconds/pin)
[+] 0.14% complete @ 2012-07-14 06:51:02 (36 seconds/pin)
[+] 0.15% complete @ 2012-07-14 06:51:48 (34 seconds/pin)

now i dont see any of the pins which are tested by reaver. 
as you can see the seconds/pin are too high. the last try took me 30 hours and 
it was @ 40% !!! this is definetly too long!

i'm using a D-Link dongle. 
excuse my bad english, i'm from germany.

Original issue reported on code.google.com by sexy_er...@hotmail.com on 14 Jul 2012 at 12:15

GoogleCodeExporter commented 8 years ago 
use -vv argument to see which pins are currently used. Possible that the router 
goes under WPS lockdowns, they usually last between 1 and 5 minutes and greatly 
inflate the s/pin number (as alot of time is wasted by waiting for the lock to 
go away).

Original comment by nexdem...@gmail.com on 27 Jul 2012 at 7:39