2 # Most of the "static" configs have been moved to here -- the command line
3 # config was getting way too crowded and cryptic. We want functionality,
4 # not continually reading --help!
6 # Version of Kismet config
7 version=2004.03.devel.a
9 # Name of server (Purely for organiational purposes)
12 # User to setid to (should be your normal user)
13 suiduser=your_user_here
15 # Sources are defined as:
16 # source=cardtype,interface,name[,initialchannel]
17 # Card types and required drivers are listed in the README.
18 # The initial channel is optional, if hopping is not enabled it can be used
19 # to set the channel the interface listens on.
20 source=hostap,wlan0,wlan0
21 source=hostap,wlan1,wlan1
22 # Other common source configs:
23 # source=prism2,wlan0,prism2source
24 # source=prism2_avs,wlan0,newprism2source
25 # source=orinoco,eth0,orinocosource
26 # An example source line with an initial channel:
27 # source=orinoco,eth0,silver,11
29 # Comma-separated list of sources to enable. This is only needed if you defined
30 # multiple sources and only want to enable some of them. By default, all defined
31 # sources are enabled.
33 # enablesources=prismsource,ciscosource
38 # How many channels per second do we hop? (1-10)
41 # By setting the dwell time for channel hopping we override the channelvelocity
42 # setting above and dwell on each channel for the given number of seconds.
45 # Do we split channels between cards on the same spectrum? This means if
46 # multiple 802.11b capture sources are defined, they will be offset to cover
47 # the most possible spectrum at a given time. This also controls splitting
48 # fine-tuned sourcechannels lines which cover multiple interfaces (see below)
51 # Basic channel hopping control:
52 # These define the channels the cards hop through for various frequency ranges
53 # supported by Kismet. More finegrain control is available via the
54 # "sourcechannels" configuration option.
56 # Don't change the IEEE80211<x> identifiers or channel hopping won't work.
58 # Users outside the US might want to use this list:
59 # defaultchannels=IEEE80211b:1,7,13,2,8,3,14,9,4,10,5,11,6,12
60 defaultchannels=IEEE80211b:1,6,11,2,7,3,8,4,9,5,10
62 # 802.11g uses the same channels as 802.11b...
63 defaultchannels=IEEE80211g:1,6,11,2,7,3,8,4,9,5,10
65 # 802.11a channels are non-overlapping so sequential is fine. You may want to
66 # adjust the list depending on the channels your card actually supports.
67 # defaultchannels=IEEE80211a:36,40,44,48,52,56,60,64,100,104,108,112,116,120,124,128,132,136,140,149,153,157,161,184,188,192,196,200,204,208,212,216
68 defaultchannels=IEEE80211a:36,40,44,48,52,56,60,64
70 # Combo cards like Atheros use both 'a' and 'b/g' channels. Of course, you
71 # can also explicitly override a given source. You can use the script
72 # extras/listchan.pl to extract all the channels your card supports.
73 defaultchannels=IEEE80211ab:1,6,11,2,7,3,8,4,9,5,10,36,40,44,48,52,56,60,64
75 # Fine-tuning channel hopping control:
76 # The sourcechannels option can be used to set the channel hopping for
77 # specific interfaces, and to control what interfaces share a list of
78 # channels for split hopping. This can also be used to easily lock
79 # one card on a single channel while hopping with other cards.
80 # Any card without a sourcechannel definition will use the standard hopping
82 # sourcechannels=sourcename[,sourcename]:ch1,ch2,ch3,...chN
84 # ie, for us channels on the source 'prism2source' (same as normal channel
86 # sourcechannels=prism2source:1,6,11,2,7,3,8,4,9,5,10
88 # Given two capture sources, "prism2a" and "prism2b", we want prism2a to stay
89 # on channel 6 and prism2b to hop normally. By not setting a sourcechannels
90 # line for prism2b, it will use the standard hopping.
91 # sourcechannels=prism2a:6
93 # To assign the same custom hop channel to multiple sources, or to split the
94 # same custom hop channel over two sources (if splitchannels is true), list
95 # them all on the same sourcechannels line:
96 # sourcechannels=prism2a,prism2b,prism2c:1,6,11
98 # Port to serve GUI data
100 # People allowed to connect, comma seperated IP addresses or network/mask
101 # blocks. Netmasks can be expressed as dotted quad (/255.255.255.0) or as
103 allowedhosts=127.0.0.1
104 # Maximum number of concurrent GUI's
109 # Host:port that GPSD is running on. This can be localhost OR remote!
110 gpshost=localhost:2947
111 # Do we lock the mode? This overrides coordinates of lock "0", which will
112 # generate some bad information until you get a GPS lock, but it will
113 # fix problems with GPS units with broken NMEA that report lock 0
116 # Packet filtering options:
117 # filter_tracker - Packets filtered from the tracker are not processed or
118 # recorded in any way.
119 # filter_dump - Packets filtered at the dump level are tracked, displayed,
120 # and written to the csv/xml/network/etc files, but not
121 # recorded in the packet dump
122 # filter_export - Controls what packets influence the exported CSV, network,
123 # xml, gps, etc files.
124 # All filtering options take arguments containing the type of address and
125 # addresses to be filtered. Valid address types are 'ANY', 'BSSID',
126 # 'SOURCE', and 'DEST'. Filtering can be inverted by the use of '!' before
127 # the address. For example,
128 # filter_tracker=ANY(!00:00:DE:AD:BE:EF)
129 # has the same effect as the previous mac_filter config file option.
134 # Alerts to be reported and the throttling rates.
135 # alert=name,throttle/unit,burst
136 # The throttle/unit describes the number of alerts of this type that are
137 # sent per time unit. Valid time units are second, minute, hour, and day.
138 # Burst describes the number of alerts sent before throttling takes place.
141 # Would allow 5 alerts through before throttling is enabled, and will then
142 # limit the number of alerts to 10 per minute.
143 # A throttle rate of 0 disables throttling of the alert.
144 # See the README for a list of alert types.
145 alert=NETSTUMBLER,5/min,2
146 alert=WELLENREITER,5/min,2
147 alert=LUCENTTEST,5/min,2
148 alert=DEAUTHFLOOD,5/min,4
149 alert=BCASTDISCON,5/min,4
150 alert=CHANCHANGE,5/min,4
151 alert=AIRJACKSSID,5/min,2
152 alert=PROBENOJOIN,5/min,2
153 alert=DISASSOCTRAFFIC,5/min,2
154 alert=NULLPROBERESP,5/min,5
156 # Known WEP keys to decrypt, bssid,hexkey. This is only for networks where
157 # the keys are already known, and it may impact throughput on slower hardware.
158 # Multiple wepkey lines may be used for multiple BSSIDs.
159 # wepkey=00:DE:AD:C0:DE:00,FEEDFACEDEADBEEF01020304050607080900
161 # Is transmission of the keys to the client allowed? This may be a security
162 # risk for some. If you disable this, you will not be able to query keys from
164 allowkeytransmit=true
166 # How often (in seconds) do we write all our data files (0 to disable)
170 # Not to be confused with GUI sound parameter, this controls wether or not the
171 # server itself will play sound. Primarily for headless or automated systems.
173 # Path to sound player
174 soundplay=/usr/bin/play
175 # Optional parameters to pass to the player
176 # soundopts=--volume=.3
178 sound_new=/usr/share/kismet/wav/new_network.wav
180 # sound_new_wep=/usr/com/kismet/wav/new_wep_network.wav
181 # Network traffic sound
182 sound_traffic=/usr/share/kismet/wav/traffic.wav
183 # Network junk traffic found
184 sound_junktraffic=/usr/share/kismet/wav/junk_traffic.wav
185 # GPS lock aquired sound
186 # sound_gpslock=/usr/share/kismet/wav/foo.wav
187 # GPS lock lost sound
188 # sound_gpslost=/usr/share/kismet/wav/bar.wav
190 sound_alert=/usr/share/kismet/wav/alert.wav
192 # Does the server have speech? (Again, not to be confused with the GUI's speech)
194 # Server's path to Festival
195 festival=/usr/bin/festival
196 # How do we speak? Valid options:
197 # speech Normal speech
198 # nato NATO spellings (alpha, bravo, charlie)
199 # spell Spell the letters out (aye, bee, sea)
201 # speech_encrypted and speech_unencrypted - Speech templates
202 # Similar to the logtemplate option, this lets you customize the speech output.
203 # speech_encrypted is used for an encrypted network spoken string
204 # speech_unencrypted is used for an unencrypted network spoken string
206 # %b is replaced by the BSSID (MAC) of the network
207 # %s is replaced by the SSID (name) of the network
208 # %c is replaced by the CHANNEL of the network
209 # %r is replaced by the MAX RATE of the network
210 speech_encrypted=New network detected, s.s.i.d. %s, channel %c, network encrypted.
211 speech_unencrypted=New network detected, s.s.i.d. %s, channel %c, network open.
213 # Where do we get our manufacturer fingerprints from? Assumed to be in the
214 # default config directory if an absolute path is not given.
216 client_manuf=client_manuf
218 # Use metric measurements in the output?
221 # Do we write waypoints for gpsdrive to load? Note: This is NOT related to
222 # recent versions of GPSDrive's native support of Kismet.
224 # GPSMap waypoint file. This WILL be truncated.
225 waypointdata=%h/.gpsdrive/way_kismet.txt
227 # How many alerts do we backlog for new clients? Only change this if you have
228 # a -very- low memory system and need those extra bytes, or if you have a high
229 # memory system and a huge number of alert conditions.
232 # File types to log, comma seperated
233 # dump - raw packet dump
234 # network - plaintext detected networks
235 # csv - plaintext detected networks in CSV format
236 # xml - XML formatted network and cisco log
237 # weak - weak packets (in airsnort format)
238 # cisco - cisco equipment CDP broadcasts
239 # gps - gps coordinates
240 logtypes=dump,network,csv,xml,weak,cisco,gps
242 # Do we track probe responses and merge probe networks into their owners?
243 # This isn't always desireable, depending on the type of monitoring you're
247 # Do we log "noise" packets that we can't decipher? I tend to not, since
248 # they don't have anything interesting at all in them.
251 # Do we log corrupt packets? Corrupt packets have enough header information
252 # to see what they are, but someting is wrong with them that prevents us from
253 # completely dissecting them. Logging these is usually not a bad idea.
256 # Do we log beacon packets or do we filter them out of the dumpfile
259 # Do we log PHY layer packets or do we filter them out of the dumpfile
262 # Do we mangle packets if we can decrypt them or if they're fuzzy-detected
265 # Do we do "fuzzy" crypt detection? (byte-based detection instead of 802.11
267 # valid option: Comma seperated list of card types to perform fuzzy detection
269 fuzzycrypt=wtapfile,wlanng,wlanng_legacy,wlanng_avs,hostap,wlanng_wext
271 # What type of dump do we generate?
272 # valid option: "wiretap"
274 # Do we limit the size of dump logs? Sometimes ethereal can't handle big ones.
276 # Anything else = Max number of packets to log to a single file before closing
277 # and opening a new one.
280 # Do we write data packets to a FIFO for an external data-IDS (such as Snort)?
281 # See the docs before enabling this.
282 #fifo=/tmp/kismet_dump
287 # logtemplate - Filename logging template.
288 # This is, at first glance, really nasty and ugly, but you'll hardly ever
289 # have to touch it so don't complain too much.
291 # %n is replaced by the logging instance name
292 # %d is replaced by the current date as Mon-DD-YYYY
293 # %D is replaced by the current date as YYYYMMDD
294 # %t is replaced by the starting log time
295 # %i is replaced by the increment log in the case of multiple logs
296 # %l is replaced by the log type (dump, status, crypt, etc)
297 # %h is replaced by the home directory
298 # ie, "netlogs/%n-%d-%i.dump" called with a logging name of "Pok" could expand
299 # to something like "netlogs/Pok-Dec-20-01-1.dump" for the first instance and
300 # "netlogs/Pok-Dec-20-01-2.%l" for the second logfile generated.
301 # %h/netlots/%n-%d-%i.dump could expand to
302 # /home/foo/netlogs/Pok-Dec-20-01-2.dump
304 # Other possibilities: Sorting by directory
305 # logtemplate=%l/%n-%d-%i
306 # Would expand to, for example,
307 # dump/Pok-Dec-20-01-1
308 # crypt/Pok-Dec-20-01-1
309 # and so on. The "dump", "crypt", etc, dirs must exist before kismet is run
311 logtemplate=/tmp/%n-%d-%i.%l
313 # Where do we store the pid file of the server?
316 # Where state info, etc, is stored. You shouldnt ever need to change this.
317 # This is a directory.
318 configdir=%h/.kismet/
320 # cloaked SSID file. You shouldn't ever need to change this.
323 # Group map file. You shouldn't ever need to change this.
326 # IP range map file. You shouldn't ever need to change this.