From owner-freebsd-current@FreeBSD.ORG Wed Nov 19 17:21:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FD9A16A4CE for ; Wed, 19 Nov 2003 17:21:00 -0800 (PST) Received: from neuroflux.com (ns1.neuroflux.com [204.228.228.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28B4C43FD7 for ; Wed, 19 Nov 2003 17:20:59 -0800 (PST) (envelope-from ryans@gamersimpact.com) Received: (qmail 63804 invoked by uid 89); 20 Nov 2003 01:20:58 -0000 Message-ID: <20031120012058.63803.qmail@neuroflux.com> References: <20031119223948.61677.qmail@neuroflux.com> <20031119230118.GA6899@perrin.nxad.com> In-Reply-To: <20031119230118.GA6899@perrin.nxad.com> From: "Ryan Sommers" To: Sean Chittenden Date: Wed, 19 Nov 2003 20:20:58 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: DStumbler / BSD-AirTools Error with new Wi code? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2003 01:21:00 -0000 I upgraded to 0.3 and installed. However, I'm still getting errors no matter how I run it: dstumbler wi0 -o error: cannot use monitor mode on non-prism2 cards dstumbler wi0 -s error: unable to ioctl device socket: Invalid argument same for just running dstumbler wi0. Any ideas? Sean Chittenden writes: >> I have been getting the following error when attempting to use dstumbler >> with 5.1-RELEASE-p10: >> >> error: unable to ioctl device socket: Invalid argument >> >> After much searching around newsgroups/mailing lists it looks like the >> Wi(4) code was changed and dstumbler never got updated. I found one patch >> that supposedly fixed support on some cards, however, it didn't seem to >> work on mine. Has anyone worked on this in -current? Or does anyone know of >> patches that aren't in CVS yet that might work? > > I just updated it yesterday. Update to 0.3 and things should work: > > dstumbler wi0 -o > > -sc > > -- > Sean Chittenden -- Ryan "leadZERO" Sommers Gamer's Impact President ryans@gamersimpact.com ICQ: 1019590 AIM/MSN: leadZERO -= http://www.gamersimpact.com =-