Kismet crashing problem

macubergeek · 06-08-2006

I've been having this problem with Kismet seg faulting.

Kismet launches and runs for a while just fine.
then it seg faults:
/usr/local/bin/kismet: line 72: 2901 segmentation fault "Didn't detect any Cisco Discovery Packets, unlinking Cisco dump."

I searched kismet.conf and found line 243
logtypes=dump,networ,cvs,xml,weak,cisco,gps

Now when I change the line to:
logtypes=dump,networ,cvs,xml,weak,gps
the above seg faulting goes away.

My question is what kismet capability am I giving up here? Am I supposed to be logging the Cisco Discovery packets?

Thorn · 06-08-2006

Quote:

Originally Posted by macubergeek

My question is what kismet capability am I giving up here?

You're giving up exactly what you thought: The Cisco Discovery packets.

Quote:

Originally Posted by macubergeek

Am I supposed to be logging the Cisco Discovery packets?

Not unless you need them for some specific purpose. I've rarely seen them (usually around large enterprise WLANS), and have never had use for them in pure WarDriving.

wrzwaldo · 06-08-2006

@ OP,

You can also do away with dump,networ, and weak if you are just wardriving.

If I recall correctly I am only logging the following when I drive.

logtypes=cvs,xml,gps

If I am doing some type of audit I will use some of the others.

Mark57 · 06-08-2006

Quote:

Originally Posted by wrzwaldo

@ OP,

You can also do away with dump,network, and weak if you are just wardriving.

If I recall correctly I am only logging the following when I drive.

logtypes=cvs,xml,gps

If I am doing some type of audit I will use some of the others.

I second that! The dump files will fill your drive quickly when you're stumbling. I only log cvs, xml, gps.

macubergeek · 06-09-2006

Thanks all
good advice.
Oddly enough Kismet's behavior differs by version. The most current version is sensitive to listing the cisco dump file. the 2005 version isn't.
No matter. I'm revising my kismet.conf to fit war driving.

06-08-2006	#1 (permalink)
macubergeek Registered Member Join Date: Aug 2004 Posts: 16	Kismet crashing problem I've been having this problem with Kismet seg faulting. Kismet launches and runs for a while just fine. then it seg faults: /usr/local/bin/kismet: line 72: 2901 segmentation fault "Didn't detect any Cisco Discovery Packets, unlinking Cisco dump." I searched kismet.conf and found line 243 logtypes=dump,networ,cvs,xml,weak,cisco,gps Now when I change the line to: logtypes=dump,networ,cvs,xml,weak,gps the above seg faulting goes away. My question is what kismet capability am I giving up here? Am I supposed to be logging the Cisco Discovery packets?

06-09-2006	#5 (permalink)
macubergeek Registered Member Join Date: Aug 2004 Posts: 16	Thanks all Thanks all good advice. Oddly enough Kismet's behavior differs by version. The most current version is sensitive to listing the cisco dump file. the 2005 version isn't. No matter. I'm revising my kismet.conf to fit war driving.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

06-08-2006	#3 (permalink)
wrzwaldo I amuse you? Join Date: Dec 2003 Posts: 9,127	@ OP, You can also do away with dump,networ, and weak if you are just wardriving. If I recall correctly I am only logging the following when I drive. logtypes=cvs,xml,gps If I am doing some type of audit I will use some of the others.