Hardware Reference
In-Depth Information
In this case, we'll run both server and client on the Pi, using the following command:
pi@raspberrypi ~ $ kismet
You'll be greeted by a colorful console interface and a series of pop-up dialog box
asking you questions about your setup. Use your
Tab
key to switch between answers
and press the
Enter
key to select. The first question about color just tweaks the color
scheme used by the Kismet interface, depending on your answer. Select
Yes
to the
second question about starting the Kismet server, then accept the default options for
the Kismet server and select
Start
.
This is the crucial point where you'll find out if your particular Wi-Fi adapter will
successfully enter monitoring mode so that Kismet can work its magic. If your adapter
doesn't support monitor mode, it will tell you so on the Kismet Server Console.
First detected network reported on Kismet Server Console
When you see messages about new detected networks starting to pop up in the log,
you know that everything is working fine and you may close the server console by
pressing the
Tab
key to select
Close Console Window,
and then pressing the
Enter
key.
You're now looking at the main Kismet screen, which is composed of different
View
areas with
Network List
being the most prominent. You'll see any number
of access points in the near vicinity and should be able to spot your own access point
in the list.
The right-hand side of the screen is the
General Info
area, which provides a grand
overview of the Kismet session, and
Packet Graph
across the middle provides a
real-time activity monitor of the packet capture process.
The
Status
area at the bottom contains the latest messages from the
Kismet Server
console and makes it easy to spot when new access points are discovered and added
to the list.
