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)?
Linux kali 3.14-kali1-amd64 #1 SMP Debian 3.14.5-1kali1 (2014-06-07) x86_64
GNU/Linux
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?
-60
4. What is the manufacturer and model # of the device you are trying to
crack?
Belkin.
5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b EC:1A:59:***** -a -S -vv -d 6
6. Please describe what you think the issue is.
The problem is restricted to a few routers, since reaver does work with some.
7. Paste the output from Reaver below.
[+] Waiting for beacon from EC:1A:59:45:95:06
[+] Switching mon0 to channel 1
[+] Associated with EC:1A:59:****** (ESSID: ***)
[+] 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
NOTES:
Reaver does work, since I am able to crack the pin of my router and I used it
with the same configuration successfully in the past.
([+] Associated with ************ (ESSID: ***)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3 message
[+] Sending M4 message
[+] Received WSC NACK
[+] Sending WSC NACK
[+] Trying pin 00005678
[+] Sending EAPOL START request
[...]
WPS is supported and not blocked as from wash.
I tried changing the mac address with macchanger to one of the device connected
to that AP but with no luck.
I tried adding "-N" etc to reaver but still, no luck.
I have to say that until an hour ago I had to use aireplay to associate because
reaver wouldn't itself (I still got the same timeout warning), then after
rebooting reaver "worked" without aireplay.
Any suggestions would be really appreciated.
Original issue reported on code.google.com by Samuli....@gmail.com on 19 Feb 2015 at 5:58
Original issue reported on code.google.com by
Samuli....@gmail.comon 19 Feb 2015 at 5:58