| < Day Day Up > |
|
After you have ensured that you have a wireless card that can be placed in monitor mode, installation of Kismet is a very straightforward process. This section details where to get the software, and how to install it on your Slackware 9.1 installation.
The latest version of Kismet is available for download from the Kismet Web site at www.kismetwireless.net/download.shtml. The current stable version of Kismet at the time of this writing is 4.0.1. If you do not want to download the most recent version, or if you would prefer to download the development version, you can browse all available versions at http://kismetwireless.net/code/.
Note | All of the examples and instructions in this Chapter use Kismet 4.0.1. If you are using a different version of Kismet, you need to change the version information in these examples as appropriate. |
After you have downloaded kismet-feb.04.01.tar.gz, uncompress and untar the package, as shown in Figure 4.27.
Figure 4.27: Uncompressing and Untarring the Kismet Files
This creates the kismet-feb.04.01 directory. Change the directory to kismet-feb.04.01, as shown in Figure 4.28.
Figure 4.28: Changing to the Kismet Directory
Now you are ready to begin configuring and installing Kismet.
Preparing to compile and install Kismet is a two-step process.
Configuring the installation script
Generating dependencies
First, you need to configure the installation script. From the kismet-feb.04.01 directory, run the configure script, as shown in Figure 4.29.
Figure 4.29: Configuring the Installation Script
The proper way to run this is with the “./” in front of configure. This indicates that the script to run is the configure script in the current, or “./” directory. Alternately, the same results could be achieved by issuing the command with the full path to configure.
Not every laptop is configured the same way. The packages installed and the hardware configurations can vary in a virtually infinite number of combinations. Kismet takes these differences into account and offers you the ability to tailor Kismet to your specific environment using special switches with the configure script.
These are the configuration switches and what they accomplish when invoked:
--disable-curses This switch disables the “curses” user interface.
--disable-panel This switch disables the panel extensions with ncurses.
--disable-gps This switch disables the Global Positioning System (GPS) support with Kismet.
--disable-netlink This switch disables netlink socket capture support.
--disable-wireless This switch disables the wireless extensions in the Linux kernel.
--disable-pcap This switch disables packet capture support using libpcap (the packet capture library).
--enable-syspcap This switch enables the system libpcap. Dragorn, the author of Kismet, does not recommend the use of this switch.
--disable-setuid This switch disables the suid cabability of Kismet. Dragorn, the author of Kismet, does not recommend the use of this switch.
--enable-wsp100 This switch enables the use of a WSP 100 remote sensor.
--enable-zaurus This switch enables extra features used by the Sharp Zaurus Personal Digital Assistant (PDA).
--enable-local-dumper This switch forces kismet to use a dump format other than Ethereal, even if Ethereal is installed on the system.
--with-ethereal=DIR This switch adds support for Ethereal wiretap logs. DIR should be replaced with the path to ethereal.
--without-ethereal This switch disables support for Ethereal wiretap logs.
--enable-acpi This switch enables Advanced Configuration and Power Interface (ACPI) support for Kismet.
To use these switches, append them to configure when it is invoked. For example, to configure Kismet without the curses interface, issue the following command: root@roamer:/home/chris/kismet-feb.04.01# ./configure –disable-curses
Note | Advanced Configuration and Power Interface (ACPI) must be enabled in the Linux kernel for this switch to work. |
Next, you need to generate dependencies using the make dep command, as shown in Figure 4.30.
Figure 4.30: Generating Dependencies
You are now ready to compile Kismet.
Once the dependencies have been generated, issuing the make command compiles Kismet using the GNU C Compiler, gcc, as shown in Figure 4.31.
Figure 4.31: Compiling Kismet
Finally, issue the make install command, as shown in Figure 4.32, to install your Kismet installation in the appropriate directories.
Figure 4.32: Installing Kismet
Unless you have an installation error, you should have an output similar to that shown in Figure 4.33.
Figure 4.33: Success!
Kismet is now installed on your computer. Before you can use Kismet you need to edit the Kismet Configuration file, kismet.conf. The configuration options are detailed in Chapter 6 of this book.
| < Day Day Up > |
|