Kismet Problems

CPUguy387 · 07-25-2004, 11:13 AM

Everytime I rum kismet, I get this error:

Code:

kismet wlan0
Server options:   wlan0
Client options:  none
Starting server...
Waiting for server to start before startuing UI...
Suid priv-dropping disabled.  This may not be secure.
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
FATAL: Illegal card source line 'wlan0'

What is wrong?

2Gnu · 07-25-2004, 11:21 AM

Post the line of your config file that defines the interface and the driver.
Is wlan0 the correct interface for your setup?

CPUguy387 · 07-25-2004, 11:27 AM

wlan0 is my wireless card. Which conf file should I post. I'm using ndiswrapper and an XP driver for my linksys card, could that have something to do with it?

2Gnu · 07-25-2004, 12:06 PM

There's a line in your Kismet configuration file that calls out the driver and interface.
/usr/local/etc/kismet.conf is the default path.
The line should look something like: source=orinoco,eth0,orinocosource

The ndiswrapper setup is probably the issue, but I've not tried it with Kismet.

CPUguy387 · 07-25-2004, 12:13 PM

It was source=cisco,eth0,ciscosource , so I tried adding wlan0 to the beginning of that line and I got this error:

Code:

FATAL: Unknown capture source type 'wlan0' in source 'wlan0,cisco,eth0,ciscosource'

And then when I changed it to just source=wlan0, I got the same old message again:

Code:

FATAL: Illegal card source line 'wlan0'

2Gnu · 07-25-2004, 12:19 PM

Your driver is not cisco and your capture source is not eth0.
Replace eth0 with wlan0 and Google for how to name the driver.
(I'd tell you that part if I knew.)

CPUguy387 · 07-25-2004, 12:28 PM

Well, the name of my driver is lsbcmnds according to ndiswrapper, so how would I out that into the source line?

CPUguy387 · 07-25-2004, 07:44 PM

Well, it turns out that ndiswrapper + kismet = BAD according to kismet's site, naturally b/c I'm using Windows drivers:

Code:

Q: Will Kismet work with Linuxant or NDISwrapper drivers?
    A: No.  These wrappers use the Windows drivers, which don't support rfmon.
       Until there are native drivers with rfmon support, Kismet won't work 
       with these cards.

So, can anybody suggest a GUI WiFi detector that will work with ndiswrapper?

Ghost_runner · 07-25-2004, 08:42 PM

linksys, don't they have native drivers, i thought they used a prism chipset?

CPUguy387 · 07-25-2004, 09:24 PM

That's what I have heard, but so far the only way I have gotten my WPC54G to work is with ndiswrapper. If anyone knows how to make my linksys wireless card work without ndiswrapper and the native chipset, thatd be GREAT!

bluntman · 07-25-2004, 10:56 PM

The WPC54G has the broadcom chipset. According to the kismet docs it is known NOT to work.

@Ghost_runner: Their cards have various chipsets. My WPC55AG has the Atheros chipset and his WPC54G has the broadcom

CPUguy387 · 07-25-2004, 11:37 PM

Ok, thx for the input, then I guess I'm back to an earlier question, is there ANY network sniffer that will work with ndiswrapper??

bluntman · 07-27-2004, 02:18 AM

There might be some active (as in NetStumbler) sniffers/detectors out there that will work. You'd have to search for them because I don't know of any.

lucas2676 · 09-25-2004, 05:56 PM

I suggest spending 20 bucks for a cisco 340 or 350 card on ebay.