Kismet Wireless

Kismet Forums


Posted by:dragorn
Subject:About kismet usability ...
Date:19:42:31 28/01/2009

> Hi, after seeing those "issues" from about 2 years, hoping in some evolution, now I want to give a pair of suggestions about kismet usability:
> 1) The kismet.conf says:
> # Source types and required drivers are listed in the README under the
> # CAPTURE SOURCES section.
> Well, is so complicated to include this list directly into the kismet.conf file? Because searching around for a README file (and every distro put this file in different places, and many people delete docs to save space, e.g. in eeepc laptops) every time is very, very annoying!!!

Yes, because it confuses people more. This was tried and failed in the past.

> 2) It's so complicated to do something like lspci | grep Wireless, and a couple of grep, sed, awk, to let kismet know by himself what damn wireless card is installed on the system? I really can't manage why in 2009 I have to tweak a config file to make a program work for me. This is very annoying and time-consumptive in many wardriving situation; having an automatic configuration of the wireless card (maybe with a chooser, in case there are 2 or more) is a great thing to do for having a more pratical and usable tool, like it has to be.

It's more complicated than you think. Newcore does significant autoconfig however many drivers such as madwifi don't make proper entries in the system for what driver is being used.

lspci is not usable because there are many cards with significantly different driver options (and more when you add users who may have configured ndis, mac80211, out of kernel, or binary vendor).


Reply to this message