Re: New stable - Kismet-Feb-04-01

Hi there,

Am Die, den 10.02.2004 schrieb Mike Kershaw um 06:01:
> New Kismet stable release is up, with 6 months of bugfixes, speed
> boosts, new features, and general good stuff, including:

Just installed the new kismet and tried to play with it a bit.

There are some strange things, I observed. Maybe one of you has come
accross this as well:

- Source specification in /etc/kismet.conf
In Kismet 3.0.1 I used "source=generic,eth1,prism54" now for 3.1.0 there
is a new integration for prism54: "source=prism54g,eth1,prism54gsource"

That's not a problem in itself. But the new integration implements
setting the mode with iwconfig. - With 3.0.1 I set manually "iwconfig
eth1 mode monitor" and fired up Kismet, afterwards "iwconfig eth1 mode
managed" put the card back to proper state. Unfortunately this is no
longer the case. OK, Kismet puts the card in monitor mode itself - but
after quitting Kismet I have to eject and re-insert my SMC2835W Cardbus
card to work again in managed mode. - A manual "iwconfig eth1 mode
managed" doesn't help either.

- The old Kismet 3.0.1 would run as "normal" user. With 3.1.0 It
wouldn't do.

First it reported to write access to create PID in /var/run (hence I
created /var/run/kismet with the appropriate rights). When I try again
after this change, I cannot access eth1 device through Kismet:

Source 0 (prism54gsource): Enabling monitor mode for prism54g source
interface eth1 channel 6...
FATAL: Unknown interface eth1: Permission denied

Currently I can help myself by launching Kismet as "root" ... but I
think this is not the intended way of doing things.

I'm eager to hear about your experiences with the new Kismet. Maybe
someone has found the hack to tweak it in user-mode.

Greets

Stefan.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQBAMknJBaGNETi6zpERAh4NAJwMEhKd3fto18Hxec1dawYCVF3iOwCePA9B
52IeLjKZvAi8guO0mmiwG+o=
=kcQj
-----END PGP SIGNATURE-----