From owner-freebsd-mobile@FreeBSD.ORG Sat Apr 8 20:23:03 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 B376C16A407 for ; Sat, 8 Apr 2006 20:23:03 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E35543D46 for ; Sat, 8 Apr 2006 20:23:03 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k38KMrPD017910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Apr 2006 13:22:54 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44381B9D.80608@errno.com> Date: Sat, 08 Apr 2006 13:22:53 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5 (X11/20060210) MIME-Version: 1.0 To: Gregers Petersen References: <20060407122442.GC10982@rebelion.Sisis.de> <44381755.3090705@cbs.dk> In-Reply-To: <44381755.3090705@cbs.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Matthias.Apitz@Sisis.de, freebsd-mobile@freebsd.org Subject: Re: 6.0-REL && iwi && wistumbler2 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 20:23:03 -0000 Gregers Petersen wrote: > guru@Sisis.de wrote: > >> but the tool 'wistumbler2' does not see anything; is it somehow broken? >> > > It is the simple problem that wistumbler2 only works with Prism based > (wi driver) chipsets -> It is my impression that a (very) few people > have made the .app work with Atheros chipsets, but I'm not able to > figure out how :-( > > You offen find the same problem when it comes to various .app's for the > monitoring of 'signal strenght' (via a gui)-> the only functional > solution I have found until now is to use 'ifconfig iwi0 scan' ..... > just as you did .. The right solution is to use bpf to collect 802.11 frames either from the 802.11 layer or from the driver. At the 802.11 layer you get raw frames. At the driver layer you get much more info (rssi, channel, etc.). This is how kismet, ethereal, etc. work. I've had patches to dstumbler for several years to do this: http://www.freebsd.org/~sam/dstumbler.tgz Some cards require that you operate in monitor mode to get interesting information. I do not know wistumbler2 to know if it works like this--but if it does then it can work with any wireless card that is properly integrated into the system. Sam