|
|
| kismet 2.4 for familiar 5.3 on an ipaq 3835 | You: 38.103.63.58 | Thursday Nov 20, 2008 8:58PM PST |
|---|
I recently purchases a Cisco Aironet 350 wireless card to use for local wireless network audits. This worked very well on my Thinkpad laptop using the excellent tool Kismet. However, I could not get it to run on my ipaq. An upgrade to the Familiar 5.3 distribution didn't help; there was a missing library. Well, there were many more problems to overcome, and they took considerable research and debugging. With a lot of help from Jerry Shenk, who had already solved most of the problems, I finally got it running. This page documents the various steps required for myself, in case I need to reinstall, and for others. This page may make it seem as though Kismet is a lot of trouble to get running, or that it was poorly put together. On the contrary, it's a great package, and works very well. The author did a great job of making a very handy tool work with myriad hardware across a plethora of platforms. (For instance, it compiled and ran without a hitch on my old Thinkpad.) I'm very grateful for the great job he did. Required ComponentsThis configuration consists of the following versions of the various pieces:
Problems and RemediesConfiguration changesAfter installing Familiar, and the Cisco wireless card (which went very smoothly for me), the next step is to obtain and install the Kismet package that is available for download from its web site. The installer runs without any output, and places everything in /usr/local/etc and /usr/local/bin. Before anything else, the configuration files must be edited. Edit kismet.conf to specify the macfilter, change the capinterface to wifi0, card type to cisco, and any other changes that one wants. I also created a /root/kismet directory and changed the logtemplate to put all logs in there. Next, edit kismet_ui.conf to set sound to true, and color to false. Missing curses libraryThe first attempt to run kismet will result in an error about a missing library. This can be obtained from /usr/lib in one of the skiffcluster machines, or it can be downloaded from here: Dropt this into /usr/lib. Just 'cos I'm thorough (read superstitious), I also created links to libpanel.so.5 and libpanel.so. Both are probably not necessary, but hey, ya' never know what some other app down the road might want:
Blank displayIncompatabilities exist in the default colors of rxvt as it is implemented on the iPaq and the colors displayed by kismet. When one does discover a nearby network, its information will be invisible. This can be overcome by launching kismet in a new terminal window set to a dark background:
No sniffing and a broken networkThe Cisco Aironet 350 works exceedingly well on the iPaq right "out of the box". At least, for a network connection, it works well. Once one discovers the right combination, it works very well for kismet, too. Unfortunately, the two settings don't work well together, and setting up a working network makes kismet inoperable and vice versa. In particular, the eth0 device must be configured by kismet for sniffing, but the wifi0 device is the one that is actually used for packet capture. Also, once the ESSID and WEP key have been reset, they don't easily obtain their former values. This results in no operation for kismet, or once it is working, no network once kismet has been run. After much experimentation, I have developed procedures that reliably switch the card between the two modes of operation. These have been put into scripts that can be used to launch kismet, and to restore network operation. Although close examination will make them appear to be very redundant (especially compaired to kismet_monitor and kismet_unmonitor), experience has shown that all steps are required. start.kismet
stop.kismet
These scripts can be obtained here, and installed in /usr/bin or /usr/local/bin to make the use of kismet as easy as issuing a single command: start.kismet. Note that start.kismet also takes care of launching an appropriate terminal window, and performing the necessary cleanup to restore network operation at the end of the run. No soundIf you have a minimal Familiar install, without the sox package, you can still play sounds. Enable sound in the config file, and create a substitute for /usr/bin/play with this command:
Next problem is that no sound files are included in the package for the ipaq. One can either grab the source distribution, or get them from here: Once obtained, create the directory where they belong, and move them there:
enjoy!
|
...dave
|
|
Top of Page | FEEDBACK Comments, Corrections & Questions welcome |
|