You are not logged in.
Pages: 1
Hey dudes and dudesses. I just installed crunchbang on my hp mini a little while ago, and its quite slick. The installation went smoothly (I installed from a usb stick) and the wireless worked fine. I carry it around in my jacket all the time and whenever I want to code I just whip it out and fire up gedit and gcc/g++/nasm/... Besides it being a very portable CS tool, I was trying to get it to do nefarious things using kismet (most notably cracking WEP networks).
However, I had some trouble getting kismet to function correctly, it gave me the error:
"FATAL: failed to set monitor mode: Invalid argument." (it then goes on to explain that this is most likely a driver problem)
my network controller, as found by "lspci" comes up as: broadcom's
"BCM4312 802.11b/g (rev 01)."
somewhat inexplicably, when i run "lspci -n" I get
"01:00.0 0280: 14e4:4315 (rev 01)" for the hardware
and when I run "airdriver-ng detect" I get two entries (after a warning that my linked kernel source doesn't match my current running version)
"Broadcom 4300" (bcm43xx) and (bcm43xx-mac80211)
the relevant line in /etc/kismet/kismet.conf that I'm using is
"source=bcm43xx,eth1,broadcom"
finally, when I try to set monitor mode manually ("iwconfig eth1 mode monitor") i get:
"SET failed on device eth1 ; Invalid Argument" which appeals to my sense of logic
I'm running kismet 2008.05.R1, as installed by apt-get.
finally, according to kismet's docs, the Broadcom 43xx cards are supported.
Could anybody help me out?
TIA,
max
Offline
At a quick look, it looks like the kernel drivers for the bcm43xx doesn't have support for monitor mode compiled in, I knew this used to be an issue for madwifi and their ilk but i'm not sure of the bcm series.
Offline
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.