From owner-freebsd-current@FreeBSD.ORG Thu Jun 21 16:56:22 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 B120816A400 for ; Thu, 21 Jun 2007 16:56:22 +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 0213413C447 for ; Thu, 21 Jun 2007 16:56:21 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 21 Jun 2007 16:56:19 -0000 Received: from h081217094222.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.94.222] by mail.gmx.net (mp025) with SMTP; 21 Jun 2007 18:56:19 +0200 X-Authenticated: #16703784 X-Provags-ID: V01U2FsdGVkX1+3x6dpbmu341yxB2uPIxmY7jy6V2KXYbvMkZDtV8 KcNcwolb8tzUVn From: Stefan Ehmann To: freebsd-current@freebsd.org Date: Thu, 21 Jun 2007 18:56:15 +0200 User-Agent: KMail/1.9.6 References: <1182410886.1320.3.camel@localhost> <467A9291.90805@errno.com> In-Reply-To: <467A9291.90805@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706211856.16123.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: "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 16:56:22 -0000 On Thursday 21 June 2007 17:00:33 Sam Leffler wrote: > Eric L. Chen wrote: > > Hi, > > I did wireless frame capture with wireshark, It works fine while I'm > > using FreeBSD-6. > > After I upgraded FreeBSD-7, I got a message: > > ieee80211_load_module: load the wlan_scan_monitor module by hand for > > now. > > > > But I can not find out 'wlan_scan_monitor' module, only wlan_scan_ap and > > wlan_scan_sta in /boot/kernel. > > You can ignore the complaint as monitor mode does not scan; you always > must set the channel. I've contemplated doing a monitor-mode scanning > module that could be used to continuously collect something like a site > survey. 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. Stefan