From owner-freebsd-current@FreeBSD.ORG Thu Jun 21 23:28:25 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 4E00316A41F for ; Thu, 21 Jun 2007 23:28:25 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2667213C457 for ; Thu, 21 Jun 2007 23:28:25 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l5LNSM7D068437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jun 2007 16:28:22 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <467B09F5.3080607@errno.com> Date: Thu, 21 Jun 2007 16:29:57 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.0 (X11/20070530) MIME-Version: 1.0 To: Stefan Ehmann References: <1182410886.1320.3.camel@localhost> <20070621201717.GA33616@tirith.brixandersen.dk> <467AE0B6.4010104@totalterror.net> <200706212256.47202.shoesoft@gmx.net> In-Reply-To: <200706212256.47202.shoesoft@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Niki Denev , 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 23:28:25 -0000 Stefan Ehmann wrote: > 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. iwi has never been a reliable packet sniffer but it sounds like a regression. FWIW iwi sniffs by "scanning a channel" but since it wasn't possible to reliably abort a scan the scan requests were made for very short periods of time and then resubmitted on timeout. This means you can easily miss frames between resubmitted scan requests. Sam