Kismet with Cisco 350 on BT3: kismet.conf trouble

[bypass]

Hi,

i've been trying to get Backtrack3 to run on my old Thinkpad X30 with built-in Cisco 350 Wifi-Adapter.
Sadly i can't seem to start up kismet.
I can however get into my own network and surf without any problem.

The Wireless Assistant reports these adapters:
eth0 and wifi0

Fiddling around with the kismet.conf [usr/local/etc/kismet.conf] i've tried:

Tried:
source=cisco,eth0,ciscosource
Error:
FATAL: pcap reported netlink type 1 (EN10MB) for eth0. This probably means you're not in RFMON mode or your drivers are reporting a bad value...

and

Tried:
source=cisco,wifi0,ciscosource
Error:
FATAL: unable to open cisco control file '/proc/driver/aironet/wifi0/Config' 2:No such file or directory. Done.

Does anybody have an idea on how to proceed?
It would be greatly appreciated.

Thanks, bypass

[tinman2k]

I've gotten this to work before. Look in the kismet.README file, I believe the correct source should be something like source=cisco_wifix,eth0:wifi0,wifi0

[theprez98]

cisco_wifix Aironet 340,350 Linux Kernel 2.4.20+, CVS
http://sourceforge.net/projects/airo-linux/
Capture interface: 'ethX:wifiX'
Kernel 2.4.20+ and CVS drivers use ethX for normal mode
and wifiX for monitor mode. Kismet needs to know both
devices, which may not necessarily be the same number,
for example 'eth1:wifi0'.
Linux kernel 2.4.20 and 2.4.21 have highly unstable cisco
drivers and should be avoided.
The cisco drivers currently do not enter rfmon mode
correctly, so channel control is not available. The
firmware will hop to whatever channel it feels like
hopping to, when it feels like hopping.

RTFM.......