I tried kismet with the latest cvs a few days ago and it was working. =
Enclosed is the output of kismet_server startup and my kismet.conf. If =
it's still not working for you, send us your kismet_server output and =
> -----Original Message-----
> From: Alexander Wirtz [mailto:lists@...]=20
> Sent: Monday, October 27, 2003 10:35 PM
> To: madwifi-devel@...
> Subject: [Madwifi-devel] Current CVS b0rks with Airsnort and Kismet
> Good morning,
> every once in a while I try running Airsnort and Kismet, and=20
> as I just=20
> tested it after updating and compiling madwifi from CVS, both=20
> failed me. Apparently the monitor-mode got b0rked when=20
> working on the proc stuff=20
> (methinks). Nevertheless, Airsnort isn't giving me any=20
> information and=20
> Kismet just leaves me with a coredump (which is like=20
> Kisuaheli to me, as=20
> it is c++)...
> Well, maybe some developer has a clue why this is happening.
> This SF.net email is sponsored by: The SF.net Donation=20
> Program. Do you like what SourceForge.net is doing for the=20
> Open Source Community? Make a contribution, and help us add=20
> new features and functionality. Click here:=20
> Madwifi-devel mailing list
thanks for the quick reply, but somehow I got it working again, albeit a
bit sluggily, though Kismet seems not to be the cause... anyway, I
included the kismet.conf for inspection, I didn't change much from the
original distributed file.
I'll try both Kismet and Airsnort on thursday at the university, lots of
APs there, maybe I can get a better picture if somethings behaving
erratically and if yes, what is really making the trouble.
Henry Qian wrote:
> I tried kismet with the latest cvs a few days ago and it was working.
> Enclosed is the output of kismet_server startup and my kismet.conf. If
> it's still not working for you, send us your kismet_server output and
> your kismet.conf.