Hardware Reference
In-Depth Information
Kismet has the option to geographically map access points using a connected GPS.
If you have a GPS that you'd like to use with Kismet, read the
Tracking the Pi's
whereabouts using GPS
section of
Chapter 5
,
Taking Your Pi Off-road
, to learn how
to set up your GPS adapter, then continue reading from here.
Kismet is also capable of alerting you of new network discoveries using sound
effects and synthesized speech. The SoX and eSpeak software from
Chapter 2
,
Audio
Antics
, works well for these purposes. In case you haven't got them installed, use the
following command to add them to your system now:
pi@raspberrypi ~ $ sudo apt-get install sox libsox-fmt-mp3 espeak
Another very important function of Kismet is to generate detailed log files.
Let's create a directory to hold these files using the following command:
pi@raspberrypi ~ $ mkdir ~/kismetlogs
Before we start Kismet, we need to open up the configuration file to adjust a few
settings to our liking, using the following command:
pi@raspberrypi ~ $ sudo nano /etc/kismet.conf
We will go through the configuration and make stops to explain or change options
from top to bottom:
•
logprefix
: Uncomment and change the
logprefix
line so that the log files
generated by Kismet will be stored in a predictable location:
logprefix=/home/pi/kismetlogs
•
ncsource
: Uncomment and change the
ncsource
line so that Kismet knows
what Wi-Fi interface to use for monitoring. There are many options for this
directive and Kismet should pick sensible defaults for the most part, but
we've specified two options here that have proved necessary in some cases
on the Pi:
ncsource=wlan0:forcevap=false,validatefcs=true
•
gps
: Change this line to read
gps=false
if you don't have a GPS attached,
otherwise leave it as it is and check that your
gpsd
is up and running.
First Kismet session
The Kismet application is actually made up of a separate server component and
client interface, which means that you could let the Pi run only the Kismet server
and then attach a client interface to it from another computer.