Date: Sat, 08 Apr 2006 13:22:53 -0700 From: Sam Leffler <sam@errno.com> To: Gregers Petersen <gp.ioa@cbs.dk> Cc: Matthias.Apitz@Sisis.de, freebsd-mobile@freebsd.org Subject: Re: 6.0-REL && iwi && wistumbler2 Message-ID: <44381B9D.80608@errno.com> In-Reply-To: <44381755.3090705@cbs.dk> References: <20060407122442.GC10982@rebelion.Sisis.de> <44381755.3090705@cbs.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44381B9D.80608>