Stuck on [+] Waiting for beacon... (Broadcom 4313 / STA drivers)

[GoogleCodeExporter]

0. What version of Reaver are you using?

Reaver 1.4 (latest)

1. What operating system are you using?
Ubuntu 11.10 / Backtrack 5R1

2. Is your wireless card in monitor mode?

Broadcom STA drivers creates an interface in monitor mode called prism0, that 
worked with airodump-ng but seems to fail with reaver.

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

70%

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

Motorola sbg900

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

reaver -i prism0 -b XX:XX:XX:XX:XX:XX -vv -c 1

6. Please describe what you think the issue is.

I think the issue is related to the STA Broadcom drivers

My card: Broadcom 4313 (wl.ko driver, latest version)

7. Paste the output from Reaver below.

If i fix the channel(-c 1) it's stuck on:

[+] Waiting for beacon from XX:XX:XX:XX:XX:XX

After waiting an hour it never did anything else.
Without fixing the channel it's hopping from channel to channel and nothing 
happens.

PD: Srry for my english.

Original issue reported on code.google.com by benignao...@gmail.com on 14 Feb 2012 at 12:32

[GoogleCodeExporter]

Your card must be set in monitor mode. The STA driver doesn't support this. Try 
it with the B43 driver.

Original comment by bungabun...@gmail.com on 15 Feb 2012 at 10:06

[GoogleCodeExporter]

Motorola sbg900 eres de argentina, es un router de fibertel.

A mi me ha pasado con los routers que quise crackear que al poner el canal este 
lanzaba errores.

hay veces que es mejor especificar el ssid que el canal:

reaver -i prism0 -b (MAC) -e (Nombre) -vv

aunque con ese driver no tienes soporte.

Original comment by demon.ia...@hotmail.com on 15 Feb 2012 at 4:54

[GoogleCodeExporter]

Hello,

I do have the same thing, I'm having a Broadcom 43228 Chipset, used the Wl 
hybrid (STA) and put my interface in monitor mode, following the README.txt 
along with the driver.

"To enable monitor mode:
$ echo 1 > /proc/brcm_monitor0

Enabling monitor mode will create a 'prism0' network interface. Wireshark and
other netwokk tools can use this new prism0 interface."

The prism0 interface works fine with airodump as the issue maker told you, but 
somehow reaver can't get beacon from the same interface

I'm quite a noob, but if airodump who needs a monitor interface works, why 
doesn't reaver on the same interface?

Original comment by Aichan...@gmail.com on 29 Apr 2014 at 9:21

[GoogleCodeExporter]

confirm: reaver not work with bcm4306 with fresh backports b43 driver
airodump collect data, aireplay test injection is work, wicd correctly connect 
to my ssid (dbm -40), but wash cant find any wps-enabled network (when my own 
ssid with wps) and reaver cant receive any beacon from my ssid when i set 
channel manually

Original comment by 624...@gmail.com on 8 Dec 2014 at 8:09