Man page of kismet_drone.conf

kismet_drone.conf

Section: (5)
Updated: Feb 24, 2003
Index of this MAN page

Back To MAN Pages From BackTrack 5 R1 Master List

NAME

kismet_drone.conf - Wireless sniffing and monitoring drone configuration file

DESCRIPTION

kismet_drone uses a minimalized configuration file, similar in options to the main kismet server configuration file. By default, the drone config is in /usr/local/etc/kismet.conf. A default configuration is included with Kismet but it is likely you will need to modify it to suit your hardware and preferences.

CONFIGURATION FILE FORMAT

All entries are of the format directive = value

CONFIGURATION VALUES

"include" (string) Include another config file.

"servername" (string) Name of this Kismet drone server. This is purely for information in multiple server systems.

"suiduser" (string) User to switch privileges to after binding to the capture.

"tcpport" (int) Port to serve streamed packet data

"allowedhosts" (string) Comma-separated list of IPs or network/mask pairs. Masks can be expressed as dotted quads (/255.255.255.0) or as numbers (/24)

"maxclient" (int) Maximum number of simultaneously connected clients

"source" (string) Comma-separated packet source (cardtype,interface,name). Multiple source lines can be defined, refer to the enablesources config line for more details.

"enablesources" (string) Comma-separated list of source names (defined previously in the source lines) to enable. This is only needed if you wish to selectively enable multiple sources. For example:

: enablesources=prism
enablesources=prism,cisco

CARD TYPES AND MULTIPLE CAPTURE SOURCES

kismet_drone supports the same sources and options as the core Kismet server. For details on supported capture types and how to define multiple capture sources, see kismet.conf(5).

Index

NAME
DESCRIPTION
CONFIGURATION FILE FORMAT
CONFIGURATION VALUES
CARD TYPES AND MULTIPLE CAPTURE SOURCES
SEE ALSO

This document was created by man2html, using the manual pages.
Time: 07:34:21 GMT, September 13, 2011

If you would like to republish one of the articles from this site on your webpage or print journal please contact IronGeek.