search

SirTheRev / reaver-wps

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

WARNING: Receive timeout occurred #214

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
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.)

RT8187L

1. What operating system are you using (Linux is the only supported OS)?

Wifiway 3.4 with the last module (includes 1.4 final)

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?

-70 with RT2500 and -47 with RT8187L

4. What is the manufacturer and model # of the device you are trying to
crack?
 Tecom 00:19:15

5. What is the entire command line string you are supplying to reaver?

reaver -i mon0 -b 00:19:15:XX.XX -vv -d 5

and -d 15 and/or -N and/or -w and/or -a etc...

6. Please describe what you think the issue is.

I have 3 equal routers, for some reason that I dont understeand, In 2 of the 3 
routers I get this error. The correct pin is 12345670 and it should work on the 
first attack. Acctually, It does in one of the 3 router, but not on the other 2.

I alredy have test other Reaver versions and I´m having the same issue.

Waiting for beacon from 00:19:15:XX:XX
Switching mon0 to channel 1
Associated with 00:19:15:XX:XX (ESSID: WLAN_XXXX)
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

And on and on....

7. Paste the output from Reaver below.

Original issue reported on code.google.com by rag...@gmail.com on 2 Feb 2012 at 10:59

GoogleCodeExporter commented 8 years ago 
i dont get the number 7. what to do ?

Original comment by tdjur...@gmail.com on 17 Feb 2012 at 2:01

GoogleCodeExporter commented 8 years ago 
The output for number 7 is on number 6, isnt it?

Original comment by rag...@gmail.com on 17 Feb 2012 at 10:21

GoogleCodeExporter commented 8 years ago 
i have the same problem,same error, same wireless card, in 2 of the 3 routers I 
get this error, what can i do?

Original comment by ionut.rz...@gmail.com on 2 Sep 2012 at 5:37

GoogleCodeExporter commented 8 years ago 
my only of this error shit what I do

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

Original comment by j4pa_...@hotmail.com on 4 Aug 2015 at 1:56