Date: Thu, 7 Oct 2010 19:34:37 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: Brandon Gooch <jamesbrandongooch@gmail.com>, net@freebsd.org Subject: Re: Monitor mode not working for iwi(4) on 7.X Message-ID: <AANLkTin08906BqMCJU2eEbpmfx=POO85c1D02EnSYLC8@mail.gmail.com> In-Reply-To: <20101007094918.GA15399@FreeBSD.org> References: <4763016D.7060100@janh.de> <20101006100335.GA26843@FreeBSD.org> <AANLkTimZD%2B8Ex2FL2cb_Z%2BTOpJV-87Z8xXhLSwtqYWmn@mail.gmail.com> <20101007094918.GA15399@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
finding where the regression happened - eg, which revision along the 6.x/head branch at the time caused the issue, would likely help Bernard very much.. Adrian 2010/10/7 Alexey Dokuchaev <danfe@freebsd.org>: > On Wed, Oct 06, 2010 at 11:56:25AM -0500, Brandon Gooch wrote: >> 2010/10/6 Alexey Dokuchaev <danfe@freebsd.org>: >> > On Fri, Dec 14, 2007 at 11:19:25PM +0100, Jan Henrik Sylvester wrote: >> >> In contrast to 6.2-RELEASE, monitor mode does not work. Kismet does >> >> not receive anything, while it does with ath or ural (even at the sam= e >> >> time). dmesg with debug.iwi=3D2 is below -- anything unusual? >> >> >> >> Moreover, "ifconfig iwi0 scan" sometimes just hangs, which never >> >> happened on 6.2-RELEASE. >> > >> > Just found this email sent to stable@ almost three years ago; sadly I >> > have to confirm iwi(4) still exhibits these problems on fairly recent >> > 7-STABLE (early Juneish). =A0Maybe I have better luck on net@ (I am >> > particularly interested in working monitor mode). =A0Thanks. =A0Any de= bug >> > information will be gladly provided. =A0Pointers where to look (revisi= ons >> > to try, patches, etc.) are greatly appreciated. >> >> I know this response isn't too helpful, but the whole Intel >> PRO/Wireless 2200BG/2225BG/2915ABG open-source driver situation is not >> too good. > > I could understand that, but it looks like FreeBSD has a *regression* > between 6.2 and 7.x, which is different from just "overall not too good > situation". =A0Regressions are presumably should not happen and should be > easier to fix than improving entire support stack in FOSS industry. =A0:-= ) > >> Same goes for the Intel 3945ABG (wpi(4)); it's very easy in both Linux >> and *BSDs to befuddle the Intel Wifi chips. >> >> Having said that, Bernhard Schmidt has made outstanding progress with >> the iwn(4) driver, supporting Intel Wireless WiFi Link >> 4965/1000/5000/5150/5300/6000/6050 series. >> >> Is it possible in your situation to try another wireless card? I know >> some notebook computers only whitelist a small set of PCI devices... > > I think there are no technical obstacles w/my laptop, and I'd gladly try > something else, preferably fully working under FreeBSD (inc. monitor > mode and packet injection). =A0Any particular recommendations (aside from > iwn(4) supported chips mentioned above)? =A0Thanks. > > ./danfe > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin08906BqMCJU2eEbpmfx=POO85c1D02EnSYLC8>