Kismet Wireless

Kismet Forums

 

Posted by:casualprogrammer
Subject:kismet-newcore not collecting packages
Date:09:25:28 25/11/2007

> > 2. It just complains about not seeing any packets. The source being ipw3945,eth1,ipw3945-source ( same as for the other flavours of kismet )
>
> Define "complains about not seeing packets"
>
> I don't have a 3945 to test with.
>
> -m

Well, I was rather imprecise, sorry.

Actually I see the UI and, apart from listing

INFO: Welcome to the Kismet Newcore Client... Press '`' or '~' to activate menu
INFO: TcpClient connected to 127.0.0.1:2501 │
INFO: Established connection with Kismet server '127.0.0.1:2501'

at the bottom, it states

[ --- No networks seen --- ]

at the top.

stopping the network service and setting monitor mode manually doesn't help any.

Log files are created, but they contain only header information.

Kismet-Nov-25-2007-1.gpsxml
Kismet-Nov-25-2007-1.nettxt
Kismet-Nov-25-2007-1.netxml
Kismet-Nov-25-2007-1.pcapdump
Kismet-Nov-25-2007-2.gpsxml
Kismet-Nov-25-2007-2.nettxt
Kismet-Nov-25-2007-2.netxml

As mentioned above, the two most recent "standard" versions of Kismet work properly.

The setting for source is always:

source=ipw3945,eth1,ipw394-source

The terminal used to start Kismet shows:

kismet
Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
INFO: Reading from config file /usr/local/etc/kismet.conf
INFO: No 'dronelisten' config line and no command line drone-listen argument
given, Kismet drone server will not be enabled.
INFO: Created alert tracker...
INFO: No specific sources named, all sources defined in kismet.conf will be
enabled.
INFO: Channel hopping enabled in config file
INFO: Channel splitting enabled in config file
INFO: Source 0 (ipw394-source): Enabling monitor mode for ipw3945 source
interface eth1 channel 6...
INFO: Capture source 'eth1' doesn't appear to use the monitor_type iwpriv
control.
INFO: Capture source 'eth1' doesn't appear to use the set_prismhdr iwpriv
control
INFO: Source 0 (ipw394-source): Opening ipw3945 source interface eth1...
INFO: Source 0 (ipw394-source): Opened source. UUID:
0000a32c-9b3c-11dc-9a83-0013021812ac
INFO: Created Kismet UI TCP server on port 2501
INFO: Kismet drone framework disabled, drone will not be activated.
INFO: Dropped privs to cjp (1000) gid 100
ERROR: Failed to open primary plugin directory (/usr/local/lib/kismet/): No
such file or directory
INFO: Inserting basic packet dissectors...
INFO: Allowing Kismet frontends to view WEP keys
INFO: Starting GPS components...
INFO: GPS support disabled in kismet.conf
INFO: Enabling reconnection to the GPS device if the link is lost
ERROR: KisNetFramework::RegisterProtocol refusing to register 'GPS' as it is
already a registered protocol.
ERROR: Could not create initial connection to the GPSD server
INFO: Using GPSD server on localhost:2947
INFO: Creating network tracker...
INFO: Probe network tracking disabled by config file
ERROR: Netracker failed to read SSID cache file version, cache file will be
replaced
ERROR: Netracker failed to read IP cache file version, cache file will be
replaced
INFO: Registering dumpfiles...
INFO: Opened pcapdump log file '/tmp/Kismet-Nov-25-2007-4.pcapdump'
INFO: Pcap log saving all beacon frames
INFO: Pcap log saving PHY frame types
INFO: Pcap log saving corrupt frames
INFO: Opened netxml log file '/tmp/Kismet-Nov-25-2007-4.netxml'
INFO: Opened nettxt log file '/tmp/Kismet-Nov-25-2007-4.nettxt'
INFO: Opened gpsxml log file '/tmp/Kismet-Nov-25-2007-4.gpsxml'
INFO: Kismet starting to gather packets
Starting UI...

*** KISMET IS FLUSHING BUFFERS AND SHUTTING DOWN ***

*** KISMET HAS ENCOUNTERED A FATAL ERROR AND CANNOT CONTINUE. ***
Kismet exiting.
Killing server...
Shutting down log files...

*** KISMET IS FLUSHING BUFFERS AND SHUTTING DOWN ***
Kismet exiting.
Kismet exited.


Let me know if I can supply more information.


Reply to this message