Kismet Wireless

Kismet Forums

 

Posted by:winguy
Subject:Kismet UI starting before server
Date:06:03:15 17/10/2008

Hi,

I have a problem with the Kismet UI starting before the server has started listening on port 2501. Below is the log of what happens when I start kismet. Any help is appreciated. Thanks.

[root@SanGu ~]# kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to kismet (498) gid 497
No specific sources given to be enabled, all will be enabled.
Disabling channel hopping.
Source 0 (madwifi): Enabling monitor mode for madwifi_ag source interface wifi0 channel 1...
WARNING: Found a non-master non-monitor VAP wifi0::ath1. Madwifi-ng has historically had problems with normal-mode VAPs combined with monitor-mode VAPs. You may need to remove them.
NOTICE: Created Madwifi-NG RFMON VAP kis0
WARNING: wifi0 appears to be using Madwifi-NG. Some versions of the Madwifi-NG drivers have problems in monitor mode, especially if non-monitor VAPs are active. If you experience problems, be sure to try the latest versions of Madwifi-NG and remove other VAPs
Source 0 (madwifi): Opening madwifi_ag source interface kis0...
Source 1 (Atheros): Enabling monitor mode for madwifi_g source interface wifi0 channel 6...
WARNING: Found a non-master non-monitor VAP wifi0::kis0. Madwifi-ng has historically had problems with normal-mode VAPs combined with monitor-mode VAPs. You may need to remove them.
NOTICE: Created Madwifi-NG RFMON VAP kis1
WARNING: wifi0 appears to be using Madwifi-NG. Some versions of the Madwifi-NG drivers have problems in monitor mode, especially if non-monitor VAPs are active. If you experience problems, be sure to try the latest versions of Madwifi-NG and remove other VAPs
Starting UI...
FATAL: Could not connect to localhost:2501.
Kismet exited.
[root@SanGu ~]# Source 1 (Atheros): Opening madwifi_g source interface kis1...
Spawned channelc control process 3338
Dropped privs to kismet (498) gid 497
Allowing clients to fetch WEP keys.
WARNING: Disabling GPS logging.
Logging networks to /var/log/kismet/Kismet-Oct-17-2008-12.network
Logging networks in CSV format to /var/log/kismet/Kismet-Oct-17-2008-12.csv
Logging networks in XML format to /var/log/kismet/Kismet-Oct-17-2008-12.xml
Logging cryptographically weak packets to /var/log/kismet/Kismet-Oct-17-2008-12.weak
Logging cisco product information to /var/log/kismet/Kismet-Oct-17-2008-12.cisco
Logging data to /var/log/kismet/Kismet-Oct-17-2008-12.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 /etc/kismet/ap_manuf
Reading client manufacturer data and defaults from /etc/kismet/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
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...


Reply to this message