Can't get monitor mode to work on a Broadcom card.

Asked by Dirk Freitag

I like to monitor my network to make sure that there isn't any erroneous neighbors connecting to my wi-fi network, and I use Kismet for this purpose. I recently bought a new netbook computer, and when I try to run Kismet, I get an error saying that monitor mode could not be enabled. Here is the full error message:

unr3a1@Un341:~$ sudo kismet
[sudo] password for unr3a1:
Launching kismet_server: //usr/bin/kismet_server
Suid priv-dropping disabled. This may not be secure.
No specific sources given to be enabled, all will be enabled.
Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng)
Enabling channel hopping.
Enabling channel splitting.
NOTICE: Disabling channel hopping, no enabled sources are able to change channel.
Source 0 (wireless): Enabling monitor mode for b43 source interface eth1 channel 6...
FATAL: Failed to set monitor mode: Invalid argument. This usually means your drivers either do not support monitor mode, or use a different mechanism for getting to it. Make sure you have a version of your drivers that support monitor mode, and consult the troubleshooting section of the README.
Done.
unr3a1@Un341:~$

I have tried to install the b43 driver firmware using b43-fwcutter, but that has not worked either. Here is the type of network card that I have (lspci -nn):

Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)

Please take note, that the card functions for everything. I can browse the web, play online games, chat on AIM. This is not an issue connecting to the internet through my wireless card. This is a problem with enabling the monitor mode on the card. Any ideas as to what I can do to get monitoring to work on this card? Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Philipp Meier
Solved:
Last query:
Last reply:
Revision history for this message
Philipp Meier (meier-philipp) said :
#1

well as the fatal part of your error message suggested,your card chip does not support monitor mode.not every card/driver does support monitor mode, did you check the kismet website about your cards chipset?
and yes monitor mode has nothing to do with the rest of the cards functionality. hope that helps a bit.

Revision history for this message
Dirk Freitag (unr3a1-r00t) said :
#2

The only thing is, that according to linuxwireless, this card DOES support monitor mode. I just don't know what I have to do to get the feature activated. I don't know if my Kismet is trying to load the improper driver, or what. I actually don' t know if loading the firmware for the card changed what "driver" I am supposed to specify in the configuration file. Is any of this a possibility?

Revision history for this message
Philipp Meier (meier-philipp) said :
#3

What happens if you press:
iwconifg "wlan0" mode monitor

??

Revision history for this message
Dirk Freitag (unr3a1-r00t) said :
#4

This is the results:

unr3a1@Un341:~$ iwconfig "eth0" mode monitor
Error for wireless request "Set Mode" (8B06) :
    SET failed on device eth0 ; Operation not permitted.
unr3a1@Un341:~$ sudo iwconfig "eth0" mode monitor
[sudo] password for unr3a1:
Error for wireless request "Set Mode" (8B06) :
    SET failed on device eth0 ; Operation not supported.
unr3a1@Un341:~$

Revision history for this message
Best Philipp Meier (meier-philipp) said :
#5

Ok so it looks like the driver you are using does not have the monitor mode feature implemented. Maybe a later version of ubuntu will deliver another driver.
If you do want to have it running no, you have two options:
1. Patch your ubuntu driver
2. or use a live version of a security distro

Revision history for this message
Dirk Freitag (unr3a1-r00t) said :
#6

Ok, I thank you for all the information that you have already provided, Mr. Meier. I just have one more question, and then I will make this question solved. I had someone else tell me that I may need to apply a patch, but they would never tell me what patch. So I ask... what patch to my drivers could I do to help this situation? Again, thank you for all your help.

Revision history for this message
Philipp Meier (meier-philipp) said :
#7

I can't tell you which patch, but google should do the job.

Revision history for this message
Dirk Freitag (unr3a1-r00t) said :
#8

Thanks Philipp Meier, that solved my question.

Revision history for this message
Dirk Freitag (unr3a1-r00t) said :
#9

Thank you for all the info. It is much appreciated.