Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is my interface blocked? "Warning: received timeout occurred" #718

Open
GoogleCodeExporter opened this issue Apr 14, 2016 · 2 comments
Open

Comments

@GoogleCodeExporter
Copy link

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

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

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?
 in my normal wifi receiver (not the one i use in wifislax) is 75%

4. What is the manufacturer and model # of the device you are trying to
crack?
 broadcom

5. What is the entire command line string you are supplying to reaver?
 reaver -i mon0 -b F8:8E:85:XX:xx:xx -vv -p 16035232 -A (earlier it worked without -A, not it only associates if i use this option)

6. Please describe what you think the issue is.
 hi, i managed more than one time to crack this bssid, and that pin works even if you change the key.

7. Paste the output from Reaver below.

[+] Trying pin 1605232
[+] 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 

is it somehow blocked? i use it with inflator, and tried more or less every 
option.. anybody can help?

Original issue reported on code.google.com by sto...@hotmail.it on 25 Apr 2015 at 3:03

@GoogleCodeExporter
Copy link
Author

anybody that might help me with this?

Original comment by sto...@hotmail.it on 6 May 2015 at 10:49

@GoogleCodeExporter
Copy link
Author

try with Bully:
bully -b f8:8e:85:xx:xx:xx -p 1605232 -B -c 5 mon0 -L

worked here!

Original comment by deltomaf...@gmail.com on 7 Aug 2015 at 3:24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant