Kismet problem

[antihaxer]

I was editing the gui config and I got an error so I reverted back to the default one and still get an error. Before I mofified the gui conf it was working perfectly.
Any ideas on how to fix it?
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Suid priv-dropping disabled. This may not be secure.
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (alfa): Enabling monitor mode for rt8180 source interface wlan0 channel 6...
Starting UI...
FATAL: Could not connect to localhost:2501.
Kismet exited.
bt ~ # Source 0 (alfa): Opening rt8180 source interface wlan0...
Allowing clients to fetch WEP keys.
Logging networks to Kismet-Jul-08-2007-10.network
Logging networks in CSV format to Kismet-Jul-08-2007-10.csv
Logging networks in XML format to Kismet-Jul-08-2007-10.xml
Logging cryptographically weak packets to Kismet-Jul-08-2007-10.weak
Logging cisco product information to Kismet-Jul-08-2007-10.cisco
Logging gps coordinates to Kismet-Jul-08-2007-10.gps
Logging data to Kismet-Jul-08-2007-10.dump
Writing data files to disk every 300 seconds.
Mangling encrypted and fuzzy data packets.
Tracking probe responses and associating probe networks.
Reading AP manufacturer data and defaults from /usr/local/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/local/etc/client_manuf
Using network-classifier based data encryption detection
Dump file format: wiretap (local code) dump
Crypt file format: airsnort (weak packet) dump
Kismet 2006.04.R1 (Kismet)
Logging data networks CSV XML weak cisco gps
GPSD cannot connect: Connection refused
Listening on port 2501.
Allowing connections from 127.0.0.1/255.255.255.255
Registering builtin client/server protocols...
Registering requested alerts...
Registering builtin timer events...
Gathering packets...
Saving data files.

[-=Xploitz=-]

I was editing the gui config and I got an error so I reverted back to the default one and still get an error. Before I mofified the gui conf it was working perfectly.

lol..tisk tisk tisk antihacker. Why do you want to go and work on something when its not broken?

[antihaxer]

Haha, I wanted to configure the gui so the mac addresses would appear. I normally use wiicrawl for that but I like kismet better. I always thought if I put the default config back it would work.

[-=Xploitz=-]

Well,

Do me a favor and post the location of your gui.conf. and the configuration file contents as well, and Il'l take a look at it for ya and offer and suggestions I see that could fix it.

[antihaxer]

media:/sda4/usr/local/etc

# Kismet GUI config file

# Version of Kismet config
version=2004.10.R1

# Do we show the intro window?
showintro=false

# Gui type to use
# Valid types: curses, panel
gui=panel
# Server to connect to (host:port)
host=localhost:2501
# Network traffic decay (active/recent/inactive) and packet click rate - increase
# this if you are doing prism2 channel hopping.
decay=3
# What columns do we display?  Comma seperated.  Read the documentation for what 
# columns are valid.
columns=decay,name,type,wep,channel,packets,flags,ip,size
# What columns do we display for clients?  Comma seperated.
clientcolumns=decay,type,mac,manuf,data,crypt,size,ip,signal,quality,noise
# Does the GUI use sound?
# NOT to be confused with "sound" option later, which is for the SERVER to make
# noise on whatever host it's running on.
sound=true
# Path to sound player
soundplay=/usr/bin/play
# Optional parameters to pass to the player
# soundopts=--volume=.3
# New network found
sound_new=/usr/local/share/kismet/wav/new_network.wav
# Wepped new network
# sound_new_wep=${prefix}/com/kismet/wav/new_wep_network.wav
# Network traffic sound
sound_traffic=/usr/local/share/kismet/wav/traffic.wav
# Network junk traffic found
sound_junktraffic=/usr/local/share/kismet/wav/junk_traffic.wav
# GPS lock aquired sound
# sound_gpslock=/usr/local/share/kismet/wav/foo.wav
# GPS lock lost sound
# sound_gpslost=/usr/local/share/kismet/wav/bar.wav
# Alert sound
sound_alert=/usr/local/share/kismet/wav/alert.wav

# Do we auotmatically make a group for probed networks or do we show them
# amidst other networks?
autogroup_probe=true
# Do we autogroup data-only networks?
autogroup_data=true
# Do we autogroup adhoc networks?
autogroup_adhoc=true

# Display battery status?
apm=false

# Does the GUI talk to us with Festival?
speech=false
# Where is festival located for the GUI?
festival=/usr/bin/festival
# Are we using festival light?  If so, point the above "festival" path to the
# "flite" binary.
flite=false
# How do we speak?  Valid options:
# speech    Normal speech
# nato      NATO spellings (alpha, bravo, charlie)
# spell     Spell the letters out (aye, bee, sea)
speech_type=nato
# speech_encrypted and speech_unencrypted - Speech templates
# Similar to the logtemplate option, this lets you customize the speech output.
# speech_encrypted is used for an encrypted network spoken string
# speech_unencrypted is used for an unencrypted network spoken string
#
# %b is replaced by the BSSID (MAC) of the network
# %s is replaced by the SSID (name) of the network
# %c is replaced by the CHANNEL of the network
# %r is replaced by the MAX RATE of the network
speech_encrypted=New network detected, s.s.i.d. %s, channel %c, network encrypted.
speech_unencrypted=New network detected, s.s.i.d. %s, channel %c, network open.

# Simple borders (use - and | instead of smooth vertical and horizontal
# lines.  This is required on Zaurus, and might be needed elsewhere if your
# terminal doesn't display the border characters correctly.
simpleborders=false

# Colors (front, back) of text in the panel front.  Valid colors are:
# black, red, yellow, green, blue, magenta, cyan, white
# optionally prefixed with "hi-" for bold/bright colors, ie
# hi-red, hi-yellow, hi-green, etc.

# Enable colors?  
color=true
# Background
backgroundcolor=black
# Default text
textcolor=white
# Window borders
bordercolor=green
# Titles
titlecolor=hi-white
# GPS and APM info
monitorcolor=hi-white
# WEP network color
wepcolor=hi-green
# Factory network color
factorycolor=hi-red
# Open color
opencolor=hi-yellow
# Decloaked network color
cloakcolor=hi-blue

[theprez98]

Just a recommendation when posting code or scripts: use the CODE tags (# button) as this boxes long strings of code into a window instead of making the post half the length of the page. It makes the previous post look more like this:

# Kismet GUI config file

# Version of Kismet config
version=2004.10.R1

# Do we show the intro window?
showintro=false

# Gui type to use
# Valid types: curses, panel
gui=panel
# Server to connect to (hostort)
host=localhost:2501
# Network traffic decay (active/recent/inactive) and packet click rate - increase
# this if you are doing prism2 channel hopping.
decay=3
# What columns do we display? Comma seperated. Read the documentation for what
# columns are valid.
columns=decay,name,type,wep,channel,packets,flags, ip,size
# What columns do we display for clients? Comma seperated.
clientcolumns=decay,type,mac,manuf,data,crypt,size ,ip,signal,quality,noise
# Does the GUI use sound?
# NOT to be confused with "sound" option later, which is for the SERVER to make
# noise on whatever host it's running on.
sound=true
# Path to sound player
soundplay=/usr/bin/play
# Optional parameters to pass to the player
# soundopts=--volume=.3
# New network found
sound_new=/usr/local/share/kismet/wav/new_network.wav
# Wepped new network
# sound_new_wep=${prefix}/com/kismet/wav/new_wep_network.wav
# Network traffic sound
sound_traffic=/usr/local/share/kismet/wav/traffic.wav
# Network junk traffic found
sound_junktraffic=/usr/local/share/kismet/wav/junk_traffic.wav
# GPS lock aquired sound
# sound_gpslock=/usr/local/share/kismet/wav/foo.wav
# GPS lock lost sound
# sound_gpslost=/usr/local/share/kismet/wav/bar.wav
# Alert sound
sound_alert=/usr/local/share/kismet/wav/alert.wav

# Do we auotmatically make a group for probed networks or do we show them
# amidst other networks?
autogroup_probe=true
# Do we autogroup data-only networks?
autogroup_data=true
# Do we autogroup adhoc networks?
autogroup_adhoc=true

# Display battery status?
apm=false

# Does the GUI talk to us with Festival?
speech=false
# Where is festival located for the GUI?
festival=/usr/bin/festival
# Are we using festival light? If so, point the above "festival" path to the
# "flite" binary.
flite=false
# How do we speak? Valid options:
# speech Normal speech
# nato NATO spellings (alpha, bravo, charlie)
# spell Spell the letters out (aye, bee, sea)
speech_type=nato
# speech_encrypted and speech_unencrypted - Speech templates
# Similar to the logtemplate option, this lets you customize the speech output.
# speech_encrypted is used for an encrypted network spoken string
# speech_unencrypted is used for an unencrypted network spoken string
#
# %b is replaced by the BSSID (MAC) of the network
# %s is replaced by the SSID (name) of the network
# %c is replaced by the CHANNEL of the network
# %r is replaced by the MAX RATE of the network
speech_encrypted=New network detected, s.s.i.d. %s, channel %c, network encrypted.
speech_unencrypted=New network detected, s.s.i.d. %s, channel %c, network open.

# Simple borders (use - and | instead of smooth vertical and horizontal
# lines. This is required on Zaurus, and might be needed elsewhere if your
# terminal doesn't display the border characters correctly.
simpleborders=false

# Colors (front, back) of text in the panel front. Valid colors are:
# black, red, yellow, green, blue, magenta, cyan, white
# optionally prefixed with "hi-" for bold/bright colors, ie
# hi-red, hi-yellow, hi-green, etc.

# Enable colors?
color=true
# Background
backgroundcolor=black
# Default text
textcolor=white
# Window borders
bordercolor=green
# Titles
titlecolor=hi-white
# GPS and APM info
monitorcolor=hi-white
# WEP network color
wepcolor=hi-green
# Factory network color
factorycolor=hi-red
# Open color
opencolor=hi-yellow
# Decloaked network color
cloakcolor=hi-blue

Thanks!

[-=Xploitz=-]

Heres mine..but it was under kismet_ui.conf in the same location as yours...

you may want to cxopy / paste it to yours. Also If that dosent work...update your kismet here....

svn co http://svn.kismetwireless.net/code/trunk kismet-devel

while cxonnecxted to the internet under Linux type the above command in a shell window EXACTLY

then do
cd /kismet-devel
hit enter
./configure
Run make dep to generate dependencies
and make followed by make install to compile and install.

now run it and if it doesn't want to corporate re-edit your kismet.conf file to the sources you need. Hope this helps you out this time.

[antihaxer]

bt kismet-devel # kismet
Server options:  none
Client options:  none
Starting server...
Waiting for server to start before starting UI...
FATAL:  Specifying a uid-0 user for the priv drop is pointless.  See the 'Installation & Security' and 'Configuration' sections of the README file for more information.

[PrairieFire]

Does anyone else notice the kismet.conf does not get updated when you update? But Kismet reports the updated version when started.



btw I used ./configure --disable-setuid

[antihaxer]

****, I edited again and it is doing the same ****ing shit. I am I not allowed to edit it or something? I tried reinstalling but no avail. It seems it has nothing to do with my ui config because i tried deleting it and kismet put the default one there and it still did not work. :/

bt kismet-devel # kismet
Server options:  none
Client options:  none
Starting server...
Waiting for server to start before starting UI...
Suid priv-dropping disabled.  This may not be secure.
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (alfa): Enabling monitor mode for rt8180 source interface wlan0 channel 6...
Source 0 (alfa): Opening rt8180 source interface wlan0...
Allowing clients to fetch WEP keys.
Logging networks to Kismet-Jul-08-2007-2.network
Logging networks in CSV format to Kismet-Jul-08-2007-2.csv
Logging networks in XML format to Kismet-Jul-08-2007-2.xml
Logging cryptographically weak packets to Kismet-Jul-08-2007-2.weak
Logging cisco product information to Kismet-Jul-08-2007-2.cisco
Logging gps coordinates to Kismet-Jul-08-2007-2.gps
Logging data to Kismet-Jul-08-2007-2.dump
Writing data files to disk every 300 seconds.
Mangling encrypted and fuzzy data packets.
Tracking probe responses and associating probe networks.
Reading AP manufacturer data and defaults from /usr/local/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/local/etc/client_manuf
Using network-classifier based data encryption detection
Dump file format: wiretap (local code) dump
Crypt file format: airsnort (weak packet) dump
Kismet 2007.01.R1 (Kismet)
Logging data networks CSV XML weak cisco gps
GPSD cannot connect: Connection refused
Listening on port 2501.
Allowing connections from 127.0.0.1/255.255.255.255
Failed to set up UI server: TcpServer bind() failed: Address already in use
Didn't detect any networks, unlinking network list.
Didn't detect any networks, unlinking CSV network list.
Didn't detect any networks, unlinking XML network list.
Didn't detect any Cisco Discovery Packets, unlinking cisco dump
Didn't capture any packets, unlinking dump file
Didn't see any weak encryption packets, unlinking weak file
WARNING: Sometimes cards don't always come out of monitor mode
         cleanly.  If your card is not fully working, you may need to
         restart or reconfigure it for normal operation.
Kismet exiting.