Kismet Wireless

Kismet Forums

 

Posted by:dt
Subject:Kismet hangs at "starting UI"
Date:22:16:37 01/10/2007

> > Insufficient info to know, sounds like your /etc/hosts or your loopback interface are screwed up and it's sitting in a DNS lookup.
> >
> > -m
>
> Loopback is on and fine, and firewall rules let everything pass to and from loopback. /etc/hosts on the other hand includes only my comp and localhost like this:
> 127.0.0.1 localhost
> 192.168.0.3 hostname
>
> 192.168.0.3 is my wired nic's static address.
>
> Why would kismet do any DNS lookups? It's a wireless sniffer for god's sake..

DITTO:
kismet_server is running fine for me (correctly handles wireless card, captures packets, the whole shebang)
the kismet user interface starts up and will not talk to the server...or console maybe?
I've tried messing with the /etc/hosts, firewall, permissions, etc...nothing seems to make any difference.
#########################
Here is my kismet output:
#########################

bash-3.1$ kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to [USERNAME] ([UID]) gid 100
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (intel): Enabling monitor mode for ipw2915 source interface eth1 channel 6...
Source 0 (intel): Opening ipw2915 source interface eth1...
Spawned channelc control process 4293
Dropped privs to [USERNAME] ([UID]) gid 100
Allowing clients to fetch WEP keys.
WARNING: Disabling GPS logging.
Logging networks to Kismet-Oct-01-2007-9.network
Logging networks in CSV format to Kismet-Oct-01-2007-9.csv
Logging networks in XML format to Kismet-Oct-01-2007-9.xml
Logging cryptographically weak packets to Kismet-Oct-01-2007-9.weak
Logging cisco product information to Kismet-Oct-01-2007-9.cisco
Logging data to Kismet-Oct-01-2007-9.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
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...
Starting UI...
FATAL: Could not connect to 127.0.0.1:2501.
Kismet exited.
bash-3.1$ Saving data files.
###############################


Reply to this message