Las víctimas

One other type of install is worth mentioning here. Some Linux distributions use the Advance Packaging Tool (APT), which is designed to greatly simplify the installation of software. The most notable of these distributions is Debian and its popular derivative, Ubuntu. To install Kismet using APT, the apt-get

command is used. Since the root user is rarely used, the sudo command must prefix the apt-get command, or the user must switch to the root user using the

su command as previously mentioned.

sudo apt-get install kismet

Running the apt-get command in this way will install Kismet in any system using the APT, and eliminates having to download and uncompress the source code, and then compile and install the program using the configure,make and

To determine which card will work under Linux and with Kismet, we first need to find out what chipset the wireless card is based upon. Chipsets are exactly what the name implies, a collection or set of integrated circuit chips that are designed to work together and produce a specific end function. In the case of wireless cards, most tend to be based on one of several chipsets.

To confuse matters further, many cards are actually the same unit, made by the same manufacturer, but sold under a different brand name label or “badge.” These “rebadged” cards will typically use the same driver as the manufacturer named card. The real trick in many cases is to figure out which card was made by what manufac- turer, and then determine what chipset was used to make the card’s hardware.

Some manufacturers will change chipsets, but will not change model names or numbers. Sometimes the manufacturer’s name changes, as in the case of a buy-out or corporate takeover, but the model names remain the same.

Finally, you will need to find out what kernel your particular Linux distro is using. The kernel is the core of a given OS. Although many drivers will work with most Linux distribution, some drivers will work differently with different Linux kernels. For example, with the introduction of kernel version 2.6.13, Linux has a new way that the drivers are able to talk to the kernel, called the “hotplug mechanism.” Some distros will have kernels below that number, while other distros will have that or a higher kernel. Some drivers will work with the hotplug mechanism, and some will not.

For example, version 0.13e-SN-9 of the ORiNOCO driver works closely with the hotplug mechanism, while the version 0.13e-SN-8 does not. Therefore, version 0.13e-SN-9 should be used with any kernel 2.6.13 or higher, where 0.13e-SN-8 card would need to be used with any Linux kernel 2.6.12 or below.

If you don’t know which kernel you have currently installed, the Linux com- mand uname -r will return the kernel version if entered at a CLI. The CLI is usually reached by a terminal or console session, or via an alternate login. For example, on one of the author’s machines, typing the command uname –r returns the result “2.4.33.3,” indicating that the kernel version is 2.4.33.3.

uname –r 2.4.33.3

The command uname –a will show all available system information. uname –a

Linux ghost 2.4.33.3 #1 Fri Sep 1 01:48:52 CDI 2006 i686 pentium3 i386 GNU/Linux For further information, typing uname –help will give a list of all available options for the command.

Once you have the kernel version, the next step is to determine the chipset used in the card. To help you figure out which cards and chipsets will work with some common wireless cards, their chipsets and their drivers are listed in Table 2.1. If your card isn’t listed here, our suggestion is that you perform a search using your favorite World Wide Web (WWW) search engine. For example, if you have an ORiNOCO Gold 11b/g Card, you would search for “ORiNOCO gold 11b/g chipset.” Adding the words “Linux “and “driver” to the search string may help you find sites where you may download a driver that will work with your particular card.

In addition, the Kismet README file has a list of known drivers and chipsets. The README file comes with the source files and is also available as a Web page at the http://www.kismetwireless.net Web site.

Table 2.1 Wireless Cards Chipsets and Linux Drivers

Chipset Driver

ADMTek ADMTek

Aironet 340, 350 Kernel 2.4.10–2.4.19, Kernel 2.4.20+, CVS

Atheros Kernel/Madwifi

Atheros madwifi; madwifi-ng

Atheros 802.11a vtar5k

Atmel-USB Berlios-Atmel

Broadcom BCM43XX

Intel/Centrino ipw2100-0.44+; ipw2200-1.0.4+; ipw3945; ipw2200/3945; iwl3945; iwl4965

Lucent, Orinoco Patched orinoco_cs; Orinoco 0.14+

Nokia/TI Nokies/TI

Prism/2 HostAP 0.4;wlan-ng 0.1.3 and earlier; wlan-ng

0.1.4–0.1.9; wlan-ng 0.2.0+ PrismGT prism54 Ralink 2400 11b rt2400-gpl, rt2500-gpl, rt73-gpl-cvs Realtek 8180 11b rtl8180-sa2400 TI ACX100 ACX100 ZyDAS USB zd1211

The same procedure can be applied to any other OS that you might be running Kismet under. Table 2.2 gives a similar listing of chipset and drivers for use with several different OSes.

There are two chipsets that are known not to work with Kismet, under any circum- stances; the Atmel and Hermes II chipsets. Additionally, a special driver used for many wireless cards is the ndiswrapper driver. The ndisdriver is used to allow some cards which only have Microsoft Windows drivers to function somewhat under Linux. Unfortunately, due to the way that the ndiswrapper works, it is not compatible with Kismet.

For our working example, we’re going to use a common and popular card, the ORiNOCO Gold 11b/g Card, Model 8470-FC, manufactured by Proxim. Following the steps above, and from looking at the chart, we know that this particular

ORiNOCO card uses the Atheros chipset, and can be run using the Madwifi driver. (See Figures 2.6 and 2.7.)

Table 2.2 Wireless Card Chipsets, Other OSes and Drivers

Cards OS Driver

Airpcap USB cygwin CACE Tech

Airport OSX viha

OSX native cards OSX/Darwin OSX

Prism/2 OpenBSD Kernel

Figure 2.7 Proxim ORiNOCO 802.11b/g Wireless Card, back Figure 2.6 Proxim ORiNOCO 802.11b/g Wireless Card, front

cd /usr/src/madwifi-0.9.4 ./configure

make

make install

When the configure,make, and make install commands have completed, the MadWifi driver has been installed. The installation process should be similar for any other wire- less card driver.