From owner-freebsd-mobile@FreeBSD.ORG Sun May 30 08:01:38 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 6744816A4CF for ; Sun, 30 May 2004 08:01:38 -0700 (PDT) Received: from poseidon.quiecom.com (poseidon.quiecom.com [66.98.144.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F74F43D45 for ; Sun, 30 May 2004 08:01:38 -0700 (PDT) (envelope-from fish@fish-mail.com) X-ClientAddr: 69.14.119.31 Received: from fifthhorseman (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 i4UF1QV05210 for ; Sun, 30 May 2004 11:01:26 -0400 From: Fish To: freebsd-mobile@freebsd.org Date: Sun, 30 May 2004 11:05:42 -0400 User-Agent: KMail/1.6.2 References: <200405200904.37966.fish@fish-mail.com> <20040525150605.GR72221@shazam.wetworks.org> <20040525200110.GY72221@shazam.wetworks.org> In-Reply-To: <20040525200110.GY72221@shazam.wetworks.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405301105.42174.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.7, required 5, BAYES_00, 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 MonitorMode 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: Sun, 30 May 2004 15:01:38 -0000 On Tuesday 25 May 2004 04:01 pm, Alan B. Clegg wrote: > Out of the ether, Alan B. Clegg spewed forth the following bitstream: > > 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). > > I must be hallucinating, as I've just done a clean re-instll from the > same media, and it acts the same way, WCPU of kismet_server going to > 107% (!), the machine going nearly comatose, and networks not being found. > > I'm now really confused as to where I need to start looking, as I don't > have a working reference point. > > Can someone that has kismet working correctly run it with stderr pointed > elsewhere and see if you get the: > > "WARNING: pcap reports link type of EN10MB but we'll fake it on BSD." > > message? > > Thanks, > AlanC I can confirm that I had the same problem as well even after a fresh reinstall from media and the installation of a few ports and their dependancies - cvsup, portupgrade, and kismet. I also have a problem with my new atheros-based card that I'm going to send an email about in a few minutes, but long story short, it says it's not hopping. Fish