Few days ago, kismet 3.0 has been released, as we can see at the project's homepage. Portage ebuild should be updated to the most recent version :-) Thanks.
Just my two cents: 1. 3.0.1 Stable is out (08/08/03) 2. News rip from http://www.kismetwireless.net: Fri Aug 08 2003 - Apparently some systems (notably Gentoo) have issues with the autoconf in kismet and libpcap. The quick fix for this is to run 'autoconf' or 'autoreconf' inside the libpcap directory, then configure Kismet. Just thought i would help if i can.
I've got the ebuild for this done, but i need to make some mild edits to the initscripts to reflect the changes in how kismet is started. As for the autoconf thing, i'm the one that sent dragorn that fix. (: i'll hopefully have this added by the week's end.
Okay, i added this in last night, without any initscripts. I'll have -r1 out soon hopefully which will include updated initscripts.
Kismet 3.01 has a bug in the initscripts or somewhere in the build itself (I DO NOT KNOW!) I just emerged it and I tried to start it after configuring it. It tries to load a program called kismet_hopper. It seems to be missing in /usr/bin/ what happen? any1 have an idea at what I should be looking at? Willing to help track this bug: jelle@Kalf.org
kismet_hopper doesn't exist anymore because the channel hopping functionality has been rolled into kismet_server.
I added rc-scripts in 3.0.1-r1. Please report feedback and I mark that stable.
Stable on x86 for a week. closing
