search

nicholasoh / reaver-wps

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

0.00% @ 0 sec/att loop #39

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
running bt5 rc 32, reaver 1.2 (no svn update)

this is what I get on 3 differents access point:

reaver -i mon0 -b 00:14:D1:50:8E:46

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

[+] Waiting for beacon from 00:14:D1:50:8E:46
[+] Associated with 00:14:D1:50:8E:46 (ESSID: house)
[+] 0.00% complete @ 0 seconds/attempt
[+] 0.00% complete @ 0 seconds/attempt
[+] 0.00% complete @ 0 seconds/attempt
[+] 0.00% complete @ 0 seconds/attempt
[+] 0.00% complete @ 0 seconds/attempt
[+] 0.00% complete @ 0 seconds/attempt
[+] 0.00% complete @ 0 seconds/attempt
[+] 0.00% complete @ 0 seconds/attempt
........

Original issue reported on code.google.com by sara.ett...@live.fr on 31 Dec 2011 at 1:58

GoogleCodeExporter commented 8 years ago 
add the -vv switch for a detailed output of what's happening.

Original comment by basti.me...@googlemail.com on 31 Dec 2011 at 2:02

GoogleCodeExporter commented 8 years ago 
...just noticed... my bad/

Original comment by sara.ett...@live.fr on 31 Dec 2011 at 2:02

GoogleCodeExporter commented 8 years ago 
Trying pin 45415500
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
+] Trying pin 45415500
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[+] Trying pin 45415500
etc....

Original comment by sara.ett...@live.fr on 31 Dec 2011 at 2:03

GoogleCodeExporter commented 8 years ago 
I think you're essentially having the same issue as mentioned here: 
http://code.google.com/p/reaver-wps/issues/detail?id=37

So we should continue posting there until the issues get merged.

Original comment by basti.me...@googlemail.com on 31 Dec 2011 at 2:06

GoogleCodeExporter commented 8 years ago 
ya same problem.... thanks

Original comment by sara.ett...@live.fr on 31 Dec 2011 at 2:17

GoogleCodeExporter commented 8 years ago 
Dup of issue #37.

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