From owner-freebsd-current@FreeBSD.ORG Thu Jun 21 20:34:01 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 D617216A41F for ; Thu, 21 Jun 2007 20:34:01 +0000 (UTC) (envelope-from niki@totalterror.net) Received: from office.suresupport.com (office.suresupport.com [213.145.98.15]) by mx1.freebsd.org (Postfix) with SMTP id EA51713C455 for ; Thu, 21 Jun 2007 20:34:00 +0000 (UTC) (envelope-from niki@totalterror.net) Received: (qmail 28757 invoked by uid 1026); 21 Jun 2007 20:33:58 -0000 Received: from 213.145.98.14 by office.suresupport.com (envelope-from , uid 1004) with qmail-scanner-2.01 (clamdscan: 0.88.4/1784. Clear:RC:1(213.145.98.14):. Processed in 0.013152 secs); 21 Jun 2007 20:33:58 -0000 Received: from unknown (HELO ndenev.office.suresupport.com) (213.145.98.14) by office.suresupport.com with SMTP; 21 Jun 2007 20:33:58 -0000 Message-ID: <467AE0B6.4010104@totalterror.net> Date: Thu, 21 Jun 2007 23:33:58 +0300 From: Niki Denev User-Agent: Thunderbird 2.0.0.0 (X11/20070531) MIME-Version: 1.0 To: Stefan Ehmann , freebsd-current@freebsd.org, "Eric L. Chen" References: <1182410886.1320.3.camel@localhost> <467A9291.90805@errno.com> <200706211856.16123.shoesoft@gmx.net> <20070621201717.GA33616@tirith.brixandersen.dk> In-Reply-To: <20070621201717.GA33616@tirith.brixandersen.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 21 Jun 2007 20:43:17 +0000 Cc: 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 20:34:01 -0000 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. Niki