Kismet Wireless

Kismet Forums

 

Posted by:smoothbooth
Subject:Kismet_Cygwin_openwrt
Date:19:56:38 23/01/2006

I have no solution for my problem.
-------------------------------------------------------------------------------
client side
-------------------------------------------------------------------------------
smoothbooth@notepad /usr/local/etc
$ kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to smoothbooth (1003) gid 513
No specific sources given to be enabled, all will be enabled.
Disabling channel hopping.
Dropped privs to smoothbooth (1003) gid 513
Source 0 (drone): Opening kismet_drone source interface 192.168.1.53:3501...
Allowing clients to fetch WEP keys.
Logging networks to Kismet-Jan-23-2006-4.network
Logging networks in CSV format to Kismet-Jan-23-2006-4.csv
Logging networks in XML format to Kismet-Jan-23-2006-4.xml
Logging cryptographically weak packets to Kismet-Jan-23-2006-4.weak
Logging cisco product information to Kismet-Jan-23-2006-4.cisco
Logging gps coordinates to Kismet-Jan-23-2006-4.gps
Logging data to Kismet-Jan-23-2006-4.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 2005.08.R1 (gateway)
Logging data networks CSV XML weak cisco gps
Opened GPS connection to localhost port 2947
Listening on port 3501.
Allowing connections from 192.168.1.53/255.255.255.255
Allowing connections from 192.168.1.101/255.255.255.255
Allowing connections from 192.168.1.102/255.255.255.255
Registering builtin client/server protocols...
Registering requested alerts...
Registering builtin timer events...
Gathering packets...
Starting UI...
Looking for startup info from 192.168.1.53:3501........................ failed.
FATAL: Did not get startup info from 192.168.1.53:3501 within 20 seconds.
Killing server...
Didn't detect any Cisco Discovery Packets, unlinking cisco dump
Didn't see any weak encryption packets, unlinking weak file
Kismet exiting.
Kismet exited.

smoothbooth@notepad /usr/local/etc
$
-------------------------------------------------------------------------------
server side
-------------------------------------------------------------------------------

WARNING: Client fd 7 ring buffer full, packet dropped.
WARNING: Client fd 7 ring buffer full, packet dropped.
WARNING: Client fd 7 ring buffer full, packet dropped.
WARNING: Client fd 7 ring buffer full, packet dropped.
WARNING: Client fd 7 ring buffer full, packet dropped.
WARNING: Killing client fd 7 read error 131: Connection reset by peer
WARNING: Killing client fd 6 read error 131: Connection reset by peer
Client fd 7 ring buffer fullAccepted streamer connection from 192.168.1.102
WARNING: Killing client fd 6 read error 131: Connection reset by peer
Accepted streamer connection from 192.168.1.102
WARNING: Killing client fd 6 read error 131: Connection reset by peer
Accepted streamer connection from 192.168.1.102
Accepted streamer connection from 192.168.1.102
WARNING: Killing client fd 7 read error 131: Connection reset by peer
WARNING: Killing client fd 6 read error 131: Connection reset by peer
-------------------------------------------------------------------------------
.
... I cry, have a wrt54g fine configured, please help!
-------------------------------------------------------------------------------
- smoothbooth


Reply to this message