Re: kismet-port

2005-07-26 Thread Pedro la Peu
> Actually, there is the strange effect that kismet _sometimes_ marks
> one of my two APs as using WEP, which is very much not the case.
> I have no idea whether that is a bug in kismet or related to iwi(4).

Some WPA AP's advertise the capability even when not enabled. We detect 
this by checking the wep bit. If you only see beacons, this won't work.



Re: kismet-port

2005-07-26 Thread Bernd Ahlers
Matthias Kilian [Tue Jul 26, 2005 at 11:59:06PM +0200] wrote:
>Here's the latest port for kismet-2005-07-R1a (a last-minute-release
>with a modified pcapsource.cc). It also makes DEBUG=-g work and
>completes Bernd's simplification (state and info files go to
>/var/log/kismet instead of /var/log/kismet/.kismet in the default
>configuration).
>
The battery time display is wrong. Naddy has a patch for it:

$OpenBSD$
--- panelfront.cc.orig  Mon Jul 25 20:41:35 2005
+++ panelfront.cc   Mon Jul 25 20:57:55 2005
@@ -1561,7 +1561,7 @@ int PanelFront::Tick() {
}
if (bat_available == 1) {
bat_percentage = (int)api.battery_life;
-   bat_time = (int)api.minutes_left;
+   bat_time = (int)api.minutes_left * 60;
if (api.battery_state == APM_BATT_CHARGING) {
bat_ac = 1;
bat_charging = 1;





Re: kismet-port

2005-07-26 Thread Matthias Kilian
On Mon, Jul 25, 2005 at 03:41:12PM +0200, Robert Nagy wrote:
> I've included a patch which fixes the problem. So with my modifications
> we can use kismet-2005-07-R1.

Here's the latest port for kismet-2005-07-R1a (a last-minute-release
with a modified pcapsource.cc). It also makes DEBUG=-g work and
completes Bernd's simplification (state and info files go to
/var/log/kismet instead of /var/log/kismet/.kismet in the default
configuration).


Pedro and Robert: the diff against the port I sent you yesterday
is minimal:

diff -rNu ../kismet/Makefile ./Makefile
--- ../kismet/Makefile  Mon Jul 25 23:59:21 2005
+++ ./Makefile  Tue Jul 26 22:13:00 2005
@@ -32,7 +32,7 @@
--sysconfdir=${CONFDIR}
 
 CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \
-   LDFLAGS="-L${LOCALBASE}/lib"
+   LDFLAGS="${LDFLAGS} -L${LOCALBASE}/lib"
 
 USE_GMAKE= Yes
 
diff -rNu ../kismet/pkg/PLIST ./pkg/PLIST
--- ../kismet/pkg/PLIST Wed Jul  6 20:56:58 2005
+++ ./pkg/PLIST Tue Jul 26 15:04:01 2005
@@ -35,4 +35,3 @@
 @owner _kismet
 @group _kismet
 @sample /var/log/kismet/
[EMAIL PROTECTED] /var/log/kismet/.kismet/



kismet.tgz
Description: application/tar-gz


Re: kismet-port

2005-07-26 Thread Matthias Kilian
On Mon, Jul 25, 2005 at 09:09:16PM +0100, Rui Reis wrote:
> Added sound support to your kismet port, works fine for me on -current.

Kismet does well without sound, so I don't see a reason for an
additional dependency to waveplay, sox, or whatever players are
available.

Ciao,
Kili



Re: kismet-port

2005-07-26 Thread Christian Weisgerber
Christian Weisgerber <[EMAIL PROTECTED]> wrote:

> iwi(4) is fine.

Actually, there is the strange effect that kismet _sometimes_ marks
one of my two APs as using WEP, which is very much not the case.
I have no idea whether that is a bug in kismet or related to iwi(4).

-- 
Christian "naddy" Weisgerber  [EMAIL PROTECTED]



Re: kismet-port

2005-07-25 Thread Matthias Kilian
On Mon, Jul 25, 2005 at 03:41:12PM +0200, Robert Nagy wrote:
> Yes, they placed a wrong #endif in pcapsource.cc.
> I've included a patch which fixes the problem. So with my modifications
> we can use kismet-2005-07-R1.

Or use kismet-2005-07-R1a they release this day.

The only flaw I noticed is with DEBUG=-g make, which currently
doesn't pass -g to the linker. May be my fault, since I did fiddling
with CFLAGS/CXXFLAGS.

Ciao,
Kili



Re: kismet-port

2005-07-25 Thread Rui Reis
On Mon, 25 Jul 2005 18:54:37 +0200
Robert Nagy <[EMAIL PROTECTED]> wrote:

> After we fixed some minor issues, yes it will go in.
> 

Added sound support to your kismet port, works fine for me on -current.

Cheers,
Rui Reis


kismet.tgz
Description: Unix tar archive


Re: kismet-port

2005-07-25 Thread Douglas Santos
On Mon, Jul 25, 2005 at 07:02:40PM +0200, Bernd Ahlers wrote:
> Robert Nagy [Mon Jul 25, 2005 at 03:41:12PM +0200] wrote:
> >Yes, they placed a wrong #endif in pcapsource.cc.
> >I've included a patch which fixes the problem. So with my modifications
> >we can use kismet-2005-07-R1.
> >The port is attached.
> >
> Works for me on i386 with an ural(4) wifi card.
> 
> I've applied a small fix for the default kismet.conf. Updated port 
> attached.
> 
> Please test.

Works fine on i386-current with iwi.



Re: kismet-port

2005-07-25 Thread Christian Weisgerber
Bernd Ahlers <[EMAIL PROTECTED]> wrote:

> Works for me on i386 with an ural(4) wifi card.

My ral(4) doesn't see any networks other than the one it was already
associated with.  It's the same for ifconfig -M, though.  Is this
a known driver limitation?

iwi(4) is fine.

-- 
Christian "naddy" Weisgerber  [EMAIL PROTECTED]



Re: kismet-port

2005-07-25 Thread Bernd Ahlers
Robert Nagy [Mon Jul 25, 2005 at 03:41:12PM +0200] wrote:
>Yes, they placed a wrong #endif in pcapsource.cc.
>I've included a patch which fixes the problem. So with my modifications
>we can use kismet-2005-07-R1.
>The port is attached.
>
Works for me on i386 with an ural(4) wifi card.

I've applied a small fix for the default kismet.conf. Updated port 
attached.

Please test.

Bernd





kismet.tgz
Description: application/tar-gz


Re: kismet-port

2005-07-25 Thread Robert Nagy
After we fixed some minor issues, yes it will go in.



Re: kismet-port

2005-07-25 Thread Marco Peereboom

Is this going in?

On Jul 25, 2005, at 8:41 AM, Robert Nagy wrote:


On (25/07/05 08:41), Matthias Kilian wrote:



If the (inofficial) kismet-2005-07-BSD will stay available for
download on the kismet site, this port can IMHO be committed.


No. We will use the offical release.



Otherwise, some additional effort is needed, since the brand-new
kismet-2005-07-R1 failed to build tomorrow (I'm very short of time,
so no details for now).


Yes, they placed a wrong #endif in pcapsource.cc.
I've included a patch which fixes the problem. So with my  
modifications

we can use kismet-2005-07-R1.
The port is attached.









Re: kismet-port

2005-07-25 Thread Robert Nagy
On (25/07/05 08:41), Matthias Kilian wrote:
> 
> If the (inofficial) kismet-2005-07-BSD will stay available for
> download on the kismet site, this port can IMHO be committed.
No. We will use the offical release.

> Otherwise, some additional effort is needed, since the brand-new
> kismet-2005-07-R1 failed to build tomorrow (I'm very short of time,
> so no details for now).
Yes, they placed a wrong #endif in pcapsource.cc.
I've included a patch which fixes the problem. So with my modifications
we can use kismet-2005-07-R1.
The port is attached.




kismet.tar.gz
Description: application/tar-gz