fabreduarte / 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 8 years ago

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