Date: Thu, 21 Jun 2007 16:29:57 -0700 From: Sam Leffler <sam@errno.com> To: Stefan Ehmann <shoesoft@gmx.net> Cc: Niki Denev <niki@totalterror.net>, freebsd-current@freebsd.org, "Eric L. Chen" <d9364104@mail.nchu.edu.tw> Subject: Re: Wireless capture Message-ID: <467B09F5.3080607@errno.com> In-Reply-To: <200706212256.47202.shoesoft@gmx.net> References: <1182410886.1320.3.camel@localhost> <20070621201717.GA33616@tirith.brixandersen.dk> <467AE0B6.4010104@totalterror.net> <200706212256.47202.shoesoft@gmx.net>
index | next in thread | previous in thread | raw e-mail
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. Samhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?467B09F5.3080607>