From owner-freebsd-mobile@FreeBSD.ORG Tue May 25 09:17:25 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F8C516A4CE for ; Tue, 25 May 2004 09:17:25 -0700 (PDT) Received: from poseidon.quiecom.com (poseidon.quiecom.com [66.98.144.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B99543D2D for ; Tue, 25 May 2004 09:17:25 -0700 (PDT) (envelope-from fish@fish-mail.com) X-ClientAddr: 69.14.119.31 Received: from somethingwicked (d14-69-31-119.try.wideopenwest.com [69.14.119.31]) (authenticated (0 bits)) by poseidon.quiecom.com (8.11.6/8.11.6) with ESMTP id i4PGGhV13456; Tue, 25 May 2004 12:16:43 -0400 From: Fish To: "Alan B. Clegg" , freebsd-mobile@freebsd.org Date: Tue, 25 May 2004 12:20:58 -0400 User-Agent: KMail/1.6.2 References: <200405200904.37966.fish@fish-mail.com> <200405200850.29662.sam@errno.com> <20040525150605.GR72221@shazam.wetworks.org> In-Reply-To: <20040525150605.GR72221@shazam.wetworks.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405251220.58498.fish@fish-mail.com> X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-38.9, required 5, BAYES_01, EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, REPLY_WITH_QUOTES, USER_AGENT_KMAIL) Subject: Re: DWL-650 & Kismet [was Re: Orinoco Wireless Card and Monitor Mode w/ Kismet - No Longer Working?] X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2004 16:17:25 -0000 On Tuesday 25 May 2004 11:06 am, you wrote: > What I've discovered is the following: > *snip* > Now, my problem. I have an up-to-date CURRENT system and all seems > to work well, with one exception. When started, kismet_server proceeds > to eat all available CPU without producing the correct located networks. > > I ran kismet (from ports) directly on a 5.2.1 (from ISO) install and > it did not display this behavior (I'm working on putting together > another system to try to reproduce the problem). > > Might anyone have a clue as to where I should start looking to see > what is going on? > > I'd really like to retire my Linux box that I use for wardriving, but... > > AlanC You say you don't see this problem on a freshly-built machine? Hm, now that IS interesting. Something, somewhere, seems to have some sort of conflict with Kismet. I'd like to help you track this down, as I'm having the exact same problem, and would like to be able to use my system for wardriving again as well. I'll get to backing up my system in preparation to rebuild, and I'll go this way: Install from CDs, install Kismet. Test. CVSUP, rebuild base system, rebuild kismet, test. Start installing ports - X, KDE3, firefox, rebuilding kismet and testing after each. It's heartening to know that I'm not the only person having this problem. Thank you, now I know there's a way to track down the problem. Fish