Part of Slepp's Projects — Pastebin — TURL — Imagebin — Filebin
Feedback -- English French German Japanese
Create Upload Newest Tools Donate

Paste Actions

Download Raw
Embed
Post to Twitter
Remove Paste

Paste Details

Raw format, 10 years 7 months old.

Advertising

Paste Description for Sartho

kismet not starting

Sartho
Sunday, June 3rd, 2007 at 1:32:16pm UTC 

  1. by Runing kismet...
  2.  
  3. [email protected]:~# kismet
  4. Server options:  none
  5. Client options:  none
  6. Starting server...
  7. Suid priv-dropping disabled.  This may not be secure.
  8. No specific sources given to be enabled, all will be enabled.
  9. Enabling channel hopping.
  10. Enabling channel splitting.
  11. Source 0 (madwifi): Enabling monitor mode for madwifi_b source interface wifi0 channel 6...
  12. WARNING: wifi0 appears to not accept the Madwifi-NG controls. Will attempt to configure it as a standard Madwifi-old interface. If you are using madwifi-ng, be sure to set the source interface to the wifiX control interface, NOT athX
  13. FATAL: GetIFFlags: interface wifi0: No such device
  14. [1] + Done(1)                    ${BIN}/kismet_server --silent ${server}
  15. Waiting for server to start before starting UI...
  16. [email protected]:~#
  17.  
  18.  
  19. My kismet.conf
  20.  
  21.  
  22. # Kismet config file
  23. # Most of the "static" configs have been moved to here -- the command line
  24. # config was getting way too crowded and cryptic.  We want functionality,
  25. # not continually reading --help!
  26.  
  27. # Version of Kismet config
  28. version=2005.06.R1
  29.  
  30. # Name of server (Purely for organizational purposes)
  31. servername=Kismet
  32.  
  33. # User to setid to (should be your normal user)
  34. #suiduser=your_user_here
  35.  
  36. # Sources are defined as:
  37. # source=sourcetype,interface,name[,initialchannel]
  38. # Source types and required drivers are listed in the README under the
  39. # CAPTURE SOURCES section.
  40. # The initial channel is optional, if hopping is not enabled it can be used
  41. # to set the channel the interface listens on.
  42. # YOU MUST CHANGE THIS TO BE THE SOURCE YOU WANT TO USE
  43.  
  44.  
  45. #source=hostap,wlan0,hostap
  46. #source=madwifi_a,ath0,madwifi
  47. #source=madwifi_b,ath0,madwifi
  48. #source=madwifi_ag,ath0,madwifi
  49. source=madwifi_b,wifi0,madwifi
  50.  
  51.  
  52. #source=madwifi,eth1,atheros,6
  53. #source=madwifi_g,eth1,addme
  54. #source=madwifi_g,ath0,atheros,8
  55. #source=madwifi_g,wifi0,AtherosG
  56.  
  57. # Comma-separated list of sources to enable.  This is only needed if you defined
  58. # multiple sources and only want to enable some of them.  By default, all defined
  59. # sources are enabled.
  60. # For example:
  61. # enablesources=prismsource,ciscosource
  62.  
  63. # Do we channelhop?
  64. channelhop=true
  65.  
  66. # How many channels per second do we hop?  (1-10)
  67. channelvelocity=5
  68.  
  69. # By setting the dwell time for channel hopping we override the channelvelocity
  70. # setting above and dwell on each channel for the given number of seconds.
  71. #channeldwell=10
  72.  
  73. # Do we split channels between cards on the same spectrum?  This means if
  74. # multiple 802.11b capture sources are defined, they will be offset to cover
  75. # the most possible spectrum at a given time.  This also controls splitting
  76. # fine-tuned sourcechannels lines which cover multiple interfaces (see below)
  77. channelsplit=true
  78.  
  79. # Basic channel hopping control:
  80. # These define the channels the cards hop through for various frequency ranges
  81. # supported by Kismet.   More finegrain control is available via the
  82. # "sourcechannels" configuration option.
  83. #
  84. # Don't change the IEEE80211<x> identifiers or channel hopping won't work.
  85.  
  86. # Users outside the US might want to use this list:
  87. # defaultchannels=IEEE80211b:1,7,13,2,8,3,14,9,4,10,5,11,6,12
  88. defaultchannels=IEEE80211b:1,6,11,2,7,3,8,4,9,5,10
  89.  
  90. # 802.11g uses the same channels as 802.11b...
  91. defaultchannels=IEEE80211g:1,6,11,2,7,3,8,4,9,5,10
  92.  
  93. # 802.11a channels are non-overlapping so sequential is fine.  You may want to
  94. # adjust the list depending on the channels your card actually supports.
  95. # 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
  96. defaultchannels=IEEE80211a:36,40,44,48,52,56,60,64
  97.  
  98. # Combo cards like Atheros use both 'a' and 'b/g' channels.  Of course, you
  99. # can also explicitly override a given source.  You can use the script
  100. # extras/listchan.pl to extract all the channels your card supports.
  101. defaultchannels=IEEE80211ab:1,6,11,2,7,3,8,4,9,5,10,36,40,44,48,52,56,60,64
  102.  
  103. # Fine-tuning channel hopping control:
  104. # The sourcechannels option can be used to set the channel hopping for
  105. # specific interfaces, and to control what interfaces share a list of
  106. # channels for split hopping.  This can also be used to easily lock
  107. # one card on a single channel while hopping with other cards.
  108. # Any card without a sourcechannel definition will use the standard hopping
  109. # list.
  110. # sourcechannels=sourcename[,sourcename]:ch1,ch2,ch3,...chN
  111.  
  112. # ie, for us channels on the source 'prism2source' (same as normal channel
  113. # hopping behavior):
  114. # sourcechannels=prism2source:1,6,11,2,7,3,8,4,9,5,10
  115.  
  116. # Given two capture sources, "prism2a" and "prism2b", we want prism2a to stay
  117. # on channel 6 and prism2b to hop normally.  By not setting a sourcechannels
  118. # line for prism2b, it will use the standard hopping.
  119. # sourcechannels=prism2a:6
  120.  
  121. # To assign the same custom hop channel to multiple sources, or to split the
  122. # same custom hop channel over two sources (if splitchannels is true), list
  123. # them all on the same sourcechannels line:
  124. # sourcechannels=prism2a,prism2b,prism2c:1,6,11
  125.  
  126. # Port to serve GUI data
  127. tcpport=2501
  128. # People allowed to connect, comma seperated IP addresses or network/mask
  129. # blocks.  Netmasks can be expressed as dotted quad (/255.255.255.0) or as
  130. # numbers (/24)
  131. allowedhosts=127.0.0.1
  132. # Address to bind to.  Should be an address already configured already on
  133. # this host, reverts to INADDR_ANY if specified incorrectly.
  134. bindaddress=127.0.0.1
  135. # Maximum number of concurrent GUI's
  136. maxclients=5
  137.  
  138. # Do we have a GPS?
  139. gps=false
  140. # Host:port that GPSD is running on.  This can be localhost OR remote!
  141. gpshost=localhost:2947
  142. # Do we lock the mode?  This overrides coordinates of lock "0", which will
  143. # generate some bad information until you get a GPS lock, but it will
  144. # fix problems with GPS units with broken NMEA that report lock 0
  145. gpsmodelock=false
  146.  
  147. # Packet filtering options:
  148. # filter_tracker - Packets filtered from the tracker are not processed or
  149. #                  recorded in any way.
  150. # filter_dump    - Packets filtered at the dump level are tracked, displayed,
  151. #                  and written to the csv/xml/network/etc files, but not
  152. #                  recorded in the packet dump
  153. # filter_export  - Controls what packets influence the exported CSV, network,
  154. #                  xml, gps, etc files.
  155. # All filtering options take arguments containing the type of address and
  156. # addresses to be filtered.  Valid address types are 'ANY', 'BSSID',
  157. # 'SOURCE', and 'DEST'.  Filtering can be inverted by the use of '!' before
  158. # the address.  For example,
  159. # filter_tracker=ANY(!00:00:DE:AD:BE:EF)
  160. # has the same effect as the previous mac_filter config file option.
  161. # filter_tracker=...
  162. # filter_dump=...
  163. # filter_export=...
  164.  
  165. # Alerts to be reported and the throttling rates.
  166. # alert=name,throttle/unit,burst/unit
  167. # The throttle/unit describes the number of alerts of this type that are
  168. # sent per time unit.  Valid time units are second, minute, hour, and day.
  169. # Burst rates control the number of packets sent at a time
  170. # For example:
  171. # alert=FOO,10/min,5/sec
  172. # Would allow 5 alerts per second, and 10 alerts total per minute.
  173. # A throttle rate of 0 disables throttling of the alert.
  174. # See the README for a list of alert types.
  175. alert=NETSTUMBLER,10/min,1/sec
  176. alert=WELLENREITER,10/min,1/sec
  177. alert=LUCENTTEST,10/min,1/sec
  178. alert=DEAUTHFLOOD,10/min,2/sec
  179. alert=BCASTDISCON,10/min,2/sec
  180. alert=CHANCHANGE,5/min,1/sec
  181. alert=AIRJACKSSID,5/min,1/sec
  182. alert=PROBENOJOIN,10/min,1/sec
  183. alert=DISASSOCTRAFFIC,10/min,1/sec
  184. alert=NULLPROBERESP,10/min,1/sec
  185. alert=BSSTIMESTAMP,10/min,1/sec
  186.  
  187. # Known WEP keys to decrypt, bssid,hexkey.  This is only for networks where
  188. # the keys are already known, and it may impact throughput on slower hardware.
  189. # Multiple wepkey lines may be used for multiple BSSIDs.
  190. # wepkey=00:DE:AD:C0:DE:00,FEEDFACEDEADBEEF01020304050607080900
  191.  
  192. # Is transmission of the keys to the client allowed?  This may be a security
  193. # risk for some.  If you disable this, you will not be able to query keys from
  194. # a client.
  195. allowkeytransmit=true
  196.  
  197. # How often (in seconds) do we write all our data files (0 to disable)
  198. writeinterval=300
  199.  
  200. # Do we use sound?
  201. # Not to be confused with GUI sound parameter, this controls wether or not the
  202. # server itself will play sound.  Primarily for headless or automated systems.
  203. sound=false
  204. # Path to sound player
  205. soundplay=/usr/bin/play
  206. # Optional parameters to pass to the player
  207. # soundopts=--volume=.3
  208. # New network found
  209. sound_new=//usr/share/kismet/wav/new_network.wav
  210. # Wepped new network
  211. # sound_new_wep=${prefix}/com/kismet/wav/new_wep_network.wav
  212. # Network traffic sound
  213. sound_traffic=//usr/share/kismet/wav/traffic.wav
  214. # Network junk traffic found
  215. sound_junktraffic=//usr/share/kismet/wav/junk_traffic.wav
  216. # GPS lock aquired sound
  217. # sound_gpslock=//usr/share/kismet/wav/foo.wav
  218. # GPS lock lost sound
  219. # sound_gpslost=//usr/share/kismet/wav/bar.wav
  220. # Alert sound
  221. sound_alert=//usr/share/kismet/wav/alert.wav
  222.  
  223. # Does the server have speech? (Again, not to be confused with the GUI's speech)
  224. speech=false
  225. # Server's path to Festival
  226. festival=/usr/bin/festival
  227. # Are we using festival lite?  If so, set the above "festival" path to also
  228. # point to the "flite" binary
  229. flite=false
  230. # How do we speak?  Valid options:
  231. # speech    Normal speech
  232. # nato      NATO spellings (alpha, bravo, charlie)
  233. # spell     Spell the letters out (aye, bee, sea)
  234. speech_type=nato
  235. # speech_encrypted and speech_unencrypted - Speech templates
  236. # Similar to the logtemplate option, this lets you customize the speech output.
  237. # speech_encrypted is used for an encrypted network spoken string
  238. #
  239. # %b is replaced by the BSSID (MAC) of the network
  240. # %s is replaced by the SSID (name) of the network
  241. # %c is replaced by the CHANNEL of the network
  242. # %r is replaced by the MAX RATE of the network
  243. speech_encrypted=New network detected, s.s.i.d. %s, channel %c, network encrypted.
  244. speech_unencrypted=New network detected, s.s.i.d. %s, channel %c, network open.
  245.  
  246. # Where do we get our manufacturer fingerprints from?  Assumed to be in the
  247. # default config directory if an absolute path is not given.
  248. ap_manuf=ap_manuf
  249. client_manuf=client_manuf
  250.  
  251. # Use metric measurements in the output?
  252. metric=false
  253.  
  254. # Do we write waypoints for gpsdrive to load?  Note:  This is NOT related to
  255. # recent versions of GPSDrive's native support of Kismet.
  256. waypoints=false
  257. # GPSDrive waypoint file.  This WILL be truncated.
  258. waypointdata=%h/.gpsdrive/way_kismet.txt
  259. # Do we want ESSID or BSSID as the waypoint name ?
  260. waypoint_essid=false
  261.  
  262. # How many alerts do we backlog for new clients?  Only change this if you have
  263. # a -very- low memory system and need those extra bytes, or if you have a high
  264. # memory system and a huge number of alert conditions.
  265. alertbacklog=50
  266.  
  267. # File types to log, comma seperated
  268. # dump    - raw packet dump
  269. # network - plaintext detected networks
  270. # csv     - plaintext detected networks in CSV format
  271. # xml     - XML formatted network and cisco log
  272. # weak    - weak packets (in airsnort format)
  273. # cisco   - cisco equipment CDP broadcasts
  274. # gps     - gps coordinates
  275. logtypes=dump,network,csv,xml,weak,cisco,gps
  276.  
  277. # Do we track probe responses and merge probe networks into their owners?
  278. # This isn't always desireable, depending on the type of monitoring you're
  279. # trying to do.
  280. trackprobenets=true
  281.  
  282. # Do we log "noise" packets that we can't decipher?  I tend to not, since
  283. # they don't have anything interesting at all in them.
  284. noiselog=false
  285.  
  286. # Do we log corrupt packets?  Corrupt packets have enough header information
  287. # to see what they are, but someting is wrong with them that prevents us from
  288. # completely dissecting them.  Logging these is usually not a bad idea.
  289. corruptlog=true
  290.  
  291. # Do we log beacon packets or do we filter them out of the dumpfile
  292. beaconlog=true
  293.  
  294. # Do we log PHY layer packets or do we filter them out of the dumpfile
  295. phylog=true
  296.  
  297. # Do we mangle packets if we can decrypt them or if they're fuzzy-detected
  298. mangledatalog=true
  299.  
  300. # Do we do "fuzzy" crypt detection?  (byte-based detection instead of 802.11
  301. # frame headers)
  302. # valid option: Comma seperated list of card types to perform fuzzy detection
  303. #  on, or 'all'
  304. fuzzycrypt=wtapfile,wlanng,wlanng_legacy,wlanng_avs,hostap,wlanng_wext,ipw2200,ipw2915
  305.  
  306. # Do we use network-classifier fuzzy-crypt detection?  This means we expect
  307. # packets that are associated with an encrypted network to be encrypted too,
  308. # and we process them by the same fuzzy compare.
  309. # This essentially replaces the fuzzycrypt per-source option.
  310. netfuzzycrypt=true
  311.  
  312. # What type of dump do we generate?
  313. # valid option: "wiretap"
  314. dumptype=wiretap
  315. # Do we limit the size of dump logs?  Sometimes ethereal can't handle big ones.
  316. # 0 = No limit
  317. # Anything else = Max number of packets to log to a single file before closing
  318. # and opening a new one.
  319. dumplimit=0
  320.  
  321. # Do we write data packets to a FIFO for an external data-IDS (such as Snort)?
  322. # See the docs before enabling this.
  323. #fifo=/tmp/kismet_dump
  324.  
  325. # Default log title
  326. logdefault=Kismet
  327.  
  328. # logtemplate - Filename logging template.
  329. # This is, at first glance, really nasty and ugly, but you'll hardly ever
  330. # have to touch it so don't complain too much.
  331. #
  332. # %n is replaced by the logging instance name
  333. # %d is replaced by the current date as Mon-DD-YYYY
  334. # %D is replaced by the current date as YYYYMMDD
  335. # %t is replaced by the starting log time
  336. # %i is replaced by the increment log in the case of multiple logs
  337. # %l is replaced by the log type (dump, status, crypt, etc)
  338. # %h is replaced by the home directory
  339. # ie, "netlogs/%n-%d-%i.dump" called with a logging name of "Pok" could expand
  340. # to something like "netlogs/Pok-Dec-20-01-1.dump" for the first instance and
  341. # "netlogs/Pok-Dec-20-01-2.%l" for the second logfile generated.
  342. # %h/netlots/%n-%d-%i.dump could expand to
  343. # /home/foo/netlogs/Pok-Dec-20-01-2.dump
  344. #
  345. # Other possibilities:  Sorting by directory
  346. # logtemplate=%l/%n-%d-%i
  347. # Would expand to, for example,
  348. # dump/Pok-Dec-20-01-1
  349. # crypt/Pok-Dec-20-01-1
  350. # and so on.  The "dump", "crypt", etc, dirs must exist before kismet is run
  351. # in this case.
  352. logtemplate=/var/log/kismet/%n-%d-%i.%l
  353.  
  354. # Where do we store the pid file of the server?
  355. piddir=/var/run/
  356.  
  357. # Where state info, etc, is stored.  You shouldnt ever need to change this.
  358. # This is a directory.
  359. configdir=/var/lib/kismet/
  360.  
  361. # cloaked SSID file.  You shouldn't ever need to change this.
  362. ssidmap=ssid_map
  363.  
  364. # Group map file.  You shouldn't ever need to change this.
  365. groupmap=group_map
  366.  
  367. # IP range map file.  You shouldn't ever need to change this.
  368. ipmap=ip_map

advertising

Update the Post

Either update this post and resubmit it with changes, or make a new post.

You may also comment on this post.

update paste below
details of the post (optional)

Note: Only the paste content is required, though the following information can be useful to others.

Save name / title?

(space separated, optional)



Please note that information posted here will not expire by default. If you do not want it to expire, please set the expiry time above. If it is set to expire, web search engines will not be allowed to index it prior to it expiring. Items that are not marked to expire will be indexable by search engines. Be careful with your passwords. All illegal activities will be reported and any information will be handed over to the authorities, so be good.

comments powered by Disqus
worth-right
worth-right
worth-right