[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201002031023.25086.holgerschurig@gmail.com>
Date: Wed, 3 Feb 2010 10:23:24 +0100
From: Holger Schurig <holgerschurig@...il.com>
To: linux-wireless@...r.kernel.org
Cc: Maxim Levitsky <maximlevitsky@...il.com>, david@...g.hm,
"Luis R. Rodriguez" <mcgrof@...il.com>,
Johannes Berg <johannes@...solutions.net>,
Witold Sowa <witold.sowa@...il.com>,
Till Kamppeter <till.kamppeter@...il.com>,
Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
lsb-discuss@...ts.linux-foundation.org
Subject: Re: Linux wireless GSoC 2010 project ideas
> Also, like I said, this should be a analysis, and not
> wardriving/hacking tool.
> And with GUI.
Please define "analysis". What exactly should be analyzed?
Kismet can do:
* construct list of all beaconing APs and IBSS devices
* associate SSID to beacons because of assoc/auth req/resp
* construct a list of all stations around
* show used protection schema
* get simple packet statistics
* get simple signal level figures
* ...
But "analysis" can obviously be much more.
Some of the analysis should also be done on driver level, e.g.
extend the nl80211-site-survey into mac80211 and add noise
reporting to some drivers (I have something preliminary for
ath5k). But also extend it to give channel occupation
statistics.
And for a GUI, you could run kismet-server in the background and
write a GUI (e.g. in Qt, so that it runs on X11/Mac/Win).
If the required analysis isn't easily put into kismet, you can of
course write a new application if you please so :-) I for
example wrote a simple Qt application that has 25% of kismet's
capability, but with a GUI. Unfortunately still Qt3.
--
http://www.holgerschurig.de
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists