Stuck on "Waiting for beacon"

GoogleCodeExporter commented 8 years ago

I am using reaver on a Fedora 16 install..

#uname -a
Linux Fedora16 3.1.5-6.fc16.i686.PAE #1 SMP Thu Dec 15 16:19:31 UTC 2011 i686 
i686 i386 GNU/Linux

The network card I am using is an Alfa Wireless AWUS035H

I grab the BSSIS from the following

# islist wlan0 

          Cell 01 - Address: 00:22:3F:39:3B:78
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=43/70  Signal level=-67 dBm  
                    Encryption key:on
                    ESSID:"burp"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              12 Mb/s; 24 Mb/s; 36 Mb/s
                    Bit Rates:9 Mb/s; 18 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000c54f399c7f
                    Extra: Last beacon: 80ms ago
                    IE: Unknown: 000462757270
                    IE: Unknown: 010882848B960C183048
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0100
                    IE: Unknown: 32041224606C
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK

# reaver -i wlan0 -b 00:22:3F:39:3B:78 -vv

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

[+] Waiting for beacon from 00:22:3F:39:3B:78

After waiting an hour it never did anything else.

Thanks for the hard work!

Original issue reported on code.google.com by trevor.e...@gmail.com on 30 Dec 2011 at 8:58

GoogleCodeExporter commented 8 years ago

Have you enabled monitor mode on your wireless card?

I had the same (non-)issue: 
http://code.google.com/p/reaver-wps/issues/detail?id=21&can=1 

You can use aircrack's airmon-ng script(http://www.aircrack-ng.org/) to get 
monitor mode on most wireless cards.

See the new wiki: http://code.google.com/p/reaver-wps/wiki/HintsAndTips

Original comment by rnd44...@gmail.com on 30 Dec 2011 at 9:10

GoogleCodeExporter commented 8 years ago

Yes, notice in your iwlist output the wlan0 interface is in "Master" mode, not 
"Monitor" mode. The monitor mode interface is likely named mon0.

Original comment by cheff...@tacnetsol.com on 30 Dec 2011 at 9:17

Changed state: Invalid

GoogleCodeExporter commented 8 years ago

Oh Duh, I will work on that. Thanks.

Original comment by trevor.e...@gmail.com on 30 Dec 2011 at 9:19

GoogleCodeExporter commented 8 years ago

Yup that and building the latest code from svn did the trick.

Just as a note so you know this works. I also installed it on a VMware 
Workstation 8 VM (also Fedora 16) and used the same hardware and it works there 
as well. So with multiple different VMs and NICs you can run multiple instances 
from one computer.

Thanks again!

Original comment by trevor.e...@gmail.com on 30 Dec 2011 at 9:47

GoogleCodeExporter commented 8 years ago

I have the monitor mode enabled on mon1 and yet I get the same message as 
trevor. Please help.

Original comment by vishalza...@gmail.com on 17 Feb 2015 at 10:15

loadProdigy / reaver-wps

Stuck on "Waiting for beacon" #29