Open GoogleCodeExporter opened 9 years ago
Others have reported problems with the rt2800usb. Updating to the latest compat
wireless drivers seems to fix it.
Does wash list your AP?
Original comment by cheff...@tacnetsol.com
on 18 Jan 2012 at 11:38
I apologize i'm quite the novice. I've been trying to figure out how to use
wash with little luck.
Original comment by gordonJe...@gmail.com
on 18 Jan 2012 at 11:43
You should just need to specify your monitor mode interface:
# wash -i mon0
Original comment by cheff...@tacnetsol.com
on 19 Jan 2012 at 12:26
[deleted comment]
This is due to the distance and signal power.
To have success on the Association, and to stop that Waiting for Beacon
message. Its simple:
You can only use reaver with AP/Routers that you are really close.
To me its only working when i have -50 or higher (-40) of signal.
Im using BackTrack the lower the better/powerfull
So get close to the AP.
Original comment by frederi...@gmail.com
on 20 Feb 2012 at 4:30
Thanks for your help, still working on it.
Original comment by GordonJe...@gmail.com
on 3 Mar 2012 at 8:54
[deleted comment]
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 3
[+] Switching mon0 to channel 4
[+] Switching mon0 to channel 6
[+] Associated with 1C:C6:3C:B9:23:DA (ESSID: Al_Etehad)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Nothing done, nothing to save.
[+] 0.00% complete @ 2013-06-21 03:32:12 (0 seconds/pin)
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[!] WARNING: 10 failed connections in a row
[+] Trying pin 12345670
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[!] WARNING: Receive timeout occurred
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x02), re-trying last pin
[+] Nothing done, nothing to save.
[+] 0.00% complete @ 2013-06-21 03:32:43 (0 second
Original comment by malika.b...@gmail.com
on 21 Jun 2013 at 7:33
@malika
I think you need to slow down your pin attempts. Try adding -d 5 to your
command. If that doesn't help try -d 15 or -d 60.
Original comment by psychede...@gmail.com
on 27 Aug 2014 at 2:08
please help me im already have the pin of my wifi neighbour but when i try
reaver it block in trying pin
Original comment by zoudjiou...@gmail.com
on 1 Sep 2014 at 11:26
hello.i'm a noob here.my
my name is Secret.
i've tried to crack a wpa wifi by using
reaver tool.
but,it just stuck at :
[+]wait for beacon ....
i couldn't understandthose the discussion above.can somebody explain to me.
Original comment by secretfa...@gmail.com
on 19 Nov 2014 at 4:47
*
You really know how much I had pushed myself
Original comment by jason.gi...@gmail.com
on 25 Jan 2015 at 7:34
[+] 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 19525679
[!] WARNING: Failed to associate with <mac> (ESSID: xxxxx)
[!] WARNING: Failed to associate with <mac> (ESSID: xxxxx)
^C
[+] Session saved.
it runs good for about 16 minutes until it fails to associate.
then I have to manually associate the AP with the command airodump-ng mon0
then i run reaver and it starts working again until it fails.
Any ideas how to automate this process?
Thank you !
Thank you !
THis is my reaver code by the way
reaver -i mon0 -b <mac> -S -N -a -c 1 -vv -r 17:30
Original comment by fraf...@gmail.com
on 15 Feb 2015 at 5:08
Original issue reported on code.google.com by
gordonJe...@gmail.com
on 18 Jan 2012 at 11:23