A few things to consider before submitting an issue:
0. We write documentation for a reason, if you have not read it and are
having problems with Reaver these pages are required reading before
submitting an issue:
http://code.google.com/p/reaver-wps/wiki/HintsAndTips
http://code.google.com/p/reaver-wps/wiki/README
http://code.google.com/p/reaver-wps/wiki/FAQ
http://code.google.com/p/reaver-wps/wiki/SupportedWirelessDrivers
1. Reaver will only work if your card is in monitor mode. If you do not
know what monitor mode is then you should learn more about 802.11 hacking
in linux before using Reaver.
2. Using Reaver against access points you do not own or have permission to
attack is illegal. If you cannot answer basic questions (i.e. model
number, distance away, etc) about the device you are attacking then do not
post your issue here. We will not help you break the law.
3. Please look through issues that have already been posted and make sure
your question has not already been asked here: http://code.google.com/p
/reaver-wps/issues/list
4. Often times we need packet captures of mon0 while Reaver is running to
troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap). Issue
reports with pcap files attached will receive more serious consideration.
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.)
v1.4
1. What operating system are you using (Linux is the only supported OS)?
Backtrack 5r3
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?
80%
4. What is the manufacturer and model # of the device you are trying to
crack?
tp-link tl-wn722 and tl-wn721 (ath9k)
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b 1C:7E:E5:XX:XX:XX -e XXXXX -c 2 -A -vv
and
reaver -i mon0 -b 1C:7E:E5:XX:XX:XX -c 2 -vv
6. Please describe what you think the issue is.
maybe there is another way to associate with AP
7. Paste the output from Reaver below.
reaver -i mon0 -b 1C:7E:E5:XX:XX:XX -e XXXXX -c 2 -A -vv
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Switching mon0 to channel 2
[+] Waiting for beacon from 1C:7E:E5:XX:XX:XX
[+] Associated with 1C:7E:E5:XX:XX:XX (ESSID: XXXXX)
[+] 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
root@bt:~# reaver -i mon2 -b 1C:7E:E5:XX:XX:XX -c 2 -vv
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Switching mon2 to channel 2
[+] Waiting for beacon from 1C:7E:E5:XX:XX:XX
and
wash -i mon0 -C
Wash v1.4 WiFi Protected Setup Scan Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
BSSID Channel RSSI WPS Version WPS Locked
ESSID
--------------------------------------------------------------------------------
-------------------------------
1C:7E:E5:XX:XX:XX 2 -54 1.0 No
XXXXX
Original issue reported on code.google.com by bar.serv...@gmail.com on 29 Apr 2013 at 4:13
Original issue reported on code.google.com by
bar.serv...@gmail.comon 29 Apr 2013 at 4:13