Friday, October 3, 2008

Installing kismet on an eeePC with default Xandros

There are hundreds of pages about installing kismet and some pages also about kismet on an eeePC (1, 2, 3..), messing everything with kismet version, Atheros vs madwifi driver, and maybe some compiling.
For a simple installation on an eeePC 900 with default Xandros, my steps were:
  1. install kismet package:
    prompt#: sudo apt-get install kismet

  2. edit "kismet.conf":
    prompt#: sudo nano /etc/kismet/kismet.conf

    by changing the "source" line (the bold one):
    # Sources are defined as:
    # source=sourcetype,interface,name[,initialchannel]
    # Source types and required drivers are listed in the README under the
    # CAPTURE SOURCES section.
    # The initial channel is optional, if hopping is not enabled it can be used
    # to set the channel the interface listens on.
    # YOU MUST CHANGE THIS TO BE THE SOURCE YOU WANT TO USE
    source=madwifi_g,wifi0,kis0

    I don't know why, but with a different "name" parameter rather than kis0, it seems not to work. I'm thinking, that leaving all the rest untouched to its default state, kismet creates its own device.



  3. make a little script:

    prompt#: sudo touch /usr/local/sbin/run-kismet
    prompt#: sudo chmod 755 /usr/local/sbin/run-kismet
    prompt#: sudo nano /usr/local/sbin/run-kismet

    it gives some commands before and after calling kismet, because some actions are needed to prepare and restore devices for connection properly:

    #!/bin/bash
    wlanconfig ath0 destroy
    sleep 2
    kismet
    sleep 2
    wlanconfig ath0 create wlandev wifi0 wlanmode sta

Now you can run kismet:
prompt#: sudo run-kismet

While your using kismet you can not connect to any wireless network; when you're done, you may re-connect as usual.