Reaver 1.4 Warning timeout occurred constant problem

[GoogleCodeExporter]

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.)reaver 1.4

1. What operating system are you using (Linux is the only supported OS)?
backtrack 5 R1
2. Is your wireless card in monitor mode (yes/no)?
yes it is in monitor mode
3. What is the signal strength of the Access Point you are trying to crack?
-36
4. What is the manufacturer and model # of the device you are trying to
crack?
alfa awus036H realtek 8171L chipset
5. What is the entire command line string you are supplying to reaver?reaver -i 
mon0 -b 1C:1D:67:2E:D0:BF -c 11 -vv

6. Please describe what you think the issue is.I keep getting this  timeout 
occured when i use backtrack 4r2 and backtrack 5r1,i know 2 of the aps are bad 
signal -55 and -72 but i got good signal with them before so the one i used is 
a strong signal,Im not very familiar with using linux os so if anyone could 
help me id appreciate it alot,would like to use reaver with ease and no 
errors.Im not sure what the problem may be thats why i came here to try and 
find a solution to this thanks
7. Paste the output from Reaver below.

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

[+] Switching mon0 to channel 11
[+] Waiting for beacon from 1C:1D:67:2E:D0:BF
[+] Associated with 1C:1D:67:2E:D0:BF (ESSID: 3MobileWiFi-d0bf)
[+] 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
[!] 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

Original issue reported on code.google.com by rushe.sp...@gmail.com on 7 Feb 2012 at 6:49

[GoogleCodeExporter]

Try adding -N -n -w -S to your command.
Or try associating with aireplay in another console (aireplay-ng mon0 -1 120 -a 
1C:1D:67:2E:D0:BF) You might want to change the channel iwconfig mon0 channel 
11 before

Helped me, sorta.

Original comment by xFxIxC...@gmail.com on 1 Mar 2012 at 2:46

[GoogleCodeExporter]

 I Have The Same prblm i tried it but still getting error

anything else for me

Original comment by 12018cm...@gmail.com on 7 Jan 2015 at 9:02