gylns / reaver-wps

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

Hung on [+] Waiting for beacon #152

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
0. What version of Reaver are you using?  (Only defects against the latest
version will be considered.)

v1.3

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

Windows 7 32bit with VMware 8 running Back Track 5 R1

2. Is your wireless card in monitor mode (yes/no)?

Yes under mon0

3. What is the signal strength of the Access Point you are trying to crack?

signal strength is -53

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

Manufacturer SMC Model # D3GN-RRR    
http://www.smc.com/files/AJ/SMCD3GN-UserManual_Rogers.pdf

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

# reaver -i mon0 -b 78:CD:8E:CD:18:99 -vv

6. Please describe what you think the issue is.

I have no idea of what the problem is :(

7. Paste the output from Reaver below.

[+] Waiting for beacon from 78:CD:8E:CD:18:99

Additional info

Modem/router has a WPS button so i assume is supports it.

CTRL + ALT produces the following
[+] Nothing done, nothing to save.
[+] Session saved.

Using Linksys WUSB100 Ralink RT2870/3070 rt2800usb

Original issue reported on code.google.com by gordonJe...@gmail.com on 18 Jan 2012 at 11:23

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
Thanks for your help, still working on it.

Original comment by GordonJe...@gmail.com on 3 Mar 2012 at 8:54

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[+] 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

GoogleCodeExporter commented 9 years ago
@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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
*
You really know how much I had pushed myself

Original comment by jason.gi...@gmail.com on 25 Jan 2015 at 7:34

GoogleCodeExporter commented 9 years ago
[+] 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

GoogleCodeExporter commented 9 years ago
Trying to attack using Mac OS 10.8.4 Using reaver

I have installed xcode, commands lines, macports

Successfully installed reaver using terminal

scanning network using KisMAC2 to find BSSID / channel / encryption etc 

trying to run the following in terminal

reaver -i en0 - 'BSSID' -c 'channel' -vv 

wireless card is going into monitor mode (can see icon changing in top menu)

then im getting stuck at the following point

Reaver v1.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[+] Switching en0 to channel 1
root required to change channel
root required to disassociate
[+] Waiting for beacon from 'BISSID'

any ideas how to get around this??? no errors are coming up im just not getting 
any action. I have tried a few different BISSID's and channels

thanks in advance 

Original comment by jacksea...@gmail.com on 4 Mar 2015 at 2:42