From: Holger Schurig <holgerschurig@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
david@lang.hm, "Luis R. Rodriguez" <mcgrof@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Witold Sowa <witold.sowa@gmail.com>,
Till Kamppeter <till.kamppeter@gmail.com>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
lsb-discuss@lists.linux-foundation.org
Subject: Re: Linux wireless GSoC 2010 project ideas
Date: Wed, 3 Feb 2010 10:23:24 +0100 [thread overview]
Message-ID: <201002031023.25086.holgerschurig@gmail.com> (raw)
In-Reply-To: <1265059913.26165.6.camel@maxim-laptop>
> 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
next prev parent reply other threads:[~2010-02-03 9:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 21:38 Linux wireless GSoC 2010 project ideas Luis R. Rodriguez
2010-01-28 22:06 ` Till Kamppeter
2010-01-28 22:14 ` Luis R. Rodriguez
2010-02-04 4:52 ` Hin-Tak Leung
2010-01-28 23:15 ` Frederic Weisbecker
2010-01-28 23:23 ` Luis R. Rodriguez
2010-01-28 23:31 ` Greg KH
2010-01-28 23:41 ` Frederic Weisbecker
2010-01-28 23:51 ` Till Kamppeter
2010-03-09 22:43 ` Frederic Weisbecker
2010-03-12 8:12 ` Till Kamppeter
2010-03-18 3:40 ` Frederic Weisbecker
2010-03-12 8:59 ` Till Kamppeter
2010-03-12 9:38 ` [lsb-discuss] " Denis Silakov
2010-03-12 9:57 ` Till Kamppeter
2010-03-21 19:49 ` Frederic Weisbecker
2010-01-31 21:03 ` Witold Sowa
2010-01-31 21:20 ` Johannes Berg
2010-02-01 18:01 ` Luis R. Rodriguez
2010-02-01 20:14 ` Maxim Levitsky
2010-02-01 20:17 ` david
2010-02-01 21:31 ` Maxim Levitsky
2010-02-03 9:23 ` Holger Schurig [this message]
2010-02-01 22:12 ` Nick Bowler
2010-02-02 4:25 ` Pat Erley
2010-02-03 9:25 ` Holger Schurig
2010-02-22 21:25 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201002031023.25086.holgerschurig@gmail.com \
--to=holgerschurig@gmail.com \
--cc=david@lang.hm \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lsb-discuss@lists.linux-foundation.org \
--cc=maximlevitsky@gmail.com \
--cc=mcgrof@gmail.com \
--cc=till.kamppeter@gmail.com \
--cc=witold.sowa@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).