Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Configuring kismet with madwifi

This page only addresses the kismet.conf configurations for the source parameter, see the kismet docs for general instructions.

You MUST have the latest development code, stable kismet only supports MadWifi-Old.

If you don't have it, you can grab latest development code with:

svn co kismet-devel

Kismet-devel will create its own VAP. You may want to remove all prior VAPs before launching kismet.
Edit kismet.conf and search for source:


See, or the README from your svn download for the most current information.

Kismet supports monitoring A, B, or G channels using one of the following sources:

  • madwifi_a
  • madwifi_ab
  • madwifi_ag
  • madwifi_g
  • madwifi_b

Be sure your capture interface is wifiX (the base device). NB: The MadWifi-Old interface is athX.

Latest SVN builds of Kismet-devel, as of 31 March 2006, autodetects whether madwifi-old, or madwifi-ng is used. Both old style and ng style capturesource statements in the kismet.conf file are supported.

And with kismet-newcore??

Somebody wrote how to use kismet-newcore, lorcon and madwifi together. A little bit complicated, but then again ...