Kismet Wireless

Kismet Forums

 

Posted by:pleriche
Subject:Kismet crashes
Date:17:32:28 19/03/2007

Provoked it again by unplugging and replugging the LAN cable. (Last time, it happened when I returned to my desk from a walkabout.) I haven't used the LAN cable much in the past, not while scanning, anyway.

Messages splurged over the screen were:
Sending termination request to channel control child 8945...
Waiting for channel control child 8945 to exit...
WARNING: Sometimes ... for normal operation.
Kismet exiting.

Status at the bottom of the Kismet (native) client says:
localhost:2501 TCP error: socket returned EOF, server has closed the connection.

It seems to be repeatable. Same happens if I don't run kismetaclient, so it's not that. I'm running on a Toshiba Tecra M1 with Intel Pro/Wireless 2100 3B wireless and Intel Pro/1000 MT Mobile LAN (DHCP), under OpenSuSe 10.2.

ifconfig (after Kismet terminates) gives:
eth3 Link encap:Ethernet HWaddr 00:08:0D:C6:D9:CD
inet addr:10.126.37.30 Bcast:10.126.37.127 Mask:255.255.255.128
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19380 errors:0 dropped:0 overruns:0 frame:0
TX packets:881 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2114613 (2.0 Mb) TX bytes:93162 (90.9 Kb)
Base address:0xcf40 Memory:dfde0000-dfe00000

eth4 Link encap:Ethernet HWaddr 00:0C:F1:0B:46:9A
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:144772 errors:6990 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13970269 (13.3 Mb) TX bytes:0 (0.0 b)
Interrupt:11 Memory:dfddf000-dfddffff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:78273 errors:0 dropped:0 overruns:0 frame:0
TX packets:78273 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13465273 (12.8 Mb) TX bytes:13465273 (12.8 Mb)

Regards - Philip

> Been successfully using Kismet daily since Jan, and for several weeks with kismetaclient. Today, it's crashed 2 or 3 times.
>
>


Reply to this message