search

MikeBiggumslol / reaver-wps

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

r33 is causeing way more timeouts than #33

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. updated from r32 to r33
2. ran reaver
3.

What is the expected output? What do you see instead?
with r32 i was getting about 2 seconds/attempt with random timeouts. r33 is 
getting mostly timeouts and slowed to 10-20 seconds/attempt.
reverting to r32 solved issue.

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

Please provide any additional information below.

Original issue reported on code.google.com by psycon...@gmail.com on 31 Dec 2011 at 2:33

GoogleCodeExporter commented 8 years ago 
Are you sure you have your revision numbers right? r33 was only a change on the 
wiki page, there were no code changes in that revision.

Original comment by cheff...@tacnetsol.com on 31 Dec 2011 at 2:52

GoogleCodeExporter commented 8 years ago 
been doing too many updates. musta been r34.

just tried again to confirm, deleted everything and started from scratch.

tested known pin and it worked.
without pin it is still going at 4-10 seconds/attempt (fluctuated up/down over 
5 mins) goes long periods on same key with timeouts (delay set to 0)

reverted to r32 again
back down to 1-2 seconds/attempt (delay still set to 0)

the spurts of timeouts seem to be totally random on my gateway, is that normal, 
i am only a foot away from the gateway, and unfortunately its logging system 
has been left out by my isp.

Original comment by psycon...@gmail.com on 31 Dec 2011 at 3:15

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
maybe its just my gateway.... its odd it goes through spurts of giving lots of 
timeouts for like 20 secs.  then half a minute without anyand reapeating that 
cycle.

running r34 again and it is going at 2seconds/attmpt now.

Original comment by psycon...@gmail.com on 31 Dec 2011 at 3:29

GoogleCodeExporter commented 8 years ago 
Are you always running with a delay of 0? I have seen APs that don't like that 
(which is why Reaver does a 1 sec delay by default). Can you provide a pcap 
file so I can see exactly where it's timing out?

Original comment by cheff...@tacnetsol.com on 31 Dec 2011 at 4:48

GoogleCodeExporter commented 8 years ago 
I've just installed the latest SVN build and it's showing constant timeouts.

(Backtrack 4 R2, AWUS036NH, rt2800usb).

Output:

root@bt:~# reaver -i mon0 -b 00:1D:7E:B5:0C:66 -c 11 -vv

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

[+] Waiting for beacon from 00:1D:7E:B5:0C:66
[+] Switching mon0 to channel 11
[+] Associated with 00:1D:7E:B5:0C:66 (ESSID: net)
[+] Trying pin 59470472
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: 25 successive start failures
[+] Trying pin 59470472
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred

Original comment by tomrile...@gmail.com on 31 Dec 2011 at 3:40

GoogleCodeExporter commented 8 years ago 
i deleted everythign again and started from scratch..  no issue.

Original comment by psycon...@gmail.com on 1 Jan 2012 at 10:50

GoogleCodeExporter commented 8 years ago 
Excellent!

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