From owner-freebsd-current@FreeBSD.ORG Thu Jun 21 21:22:43 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1CBFB16A53C for ; Thu, 21 Jun 2007 21:22:43 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 5CC0313C487 for ; Thu, 21 Jun 2007 21:22:42 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 21 Jun 2007 21:22:40 -0000 Received: from h081217094222.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.94.222] by mail.gmx.net (mp018) with SMTP; 21 Jun 2007 23:22:40 +0200 X-Authenticated: #16703784 X-Provags-ID: V01U2FsdGVkX1/0SIpwf5r0DFx/kDELa32TaV2Np65/TNIjMsLOJZ haeQvTdKg8xWN4 From: Stefan Ehmann To: Niki Denev Date: Thu, 21 Jun 2007 22:56:45 +0200 User-Agent: KMail/1.9.6 References: <1182410886.1320.3.camel@localhost> <20070621201717.GA33616@tirith.brixandersen.dk> <467AE0B6.4010104@totalterror.net> In-Reply-To: <467AE0B6.4010104@totalterror.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706212256.47202.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org, "Eric L. Chen" Subject: Re: Wireless capture X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2007 21:22:43 -0000 On Thursday 21 June 2007 22:33:58 Niki Denev wrote: > Henrik Brix Andersen wrote: > > On Thu, Jun 21, 2007 at 06:56:15PM +0200, Stefan Ehmann wrote: > >> kismet doesn't detect any APs after the 802.11 changes. I thought I had > >> to wait until someone commits the wlan_scan_monitor module. But it seems > >> like this won't help. > >> > >> Any idea why kismet stopped working? Except for the missing module, I > >> haven't seen any suspicous message. > > > > For what it's worth, kismet still works as expected on my -CURRENT box > > using the ath(4) driver. > > > > Regards, > > Brix > > I have just checked and it works here too, with ral(4) pccard. Thanks for your reports. So it's either a bug in iwi or something wrong on my side. It has worked before and I haven't changed the config though. Stefan