Date: Wed, 6 Oct 2010 11:56:25 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: net@freebsd.org Subject: Re: Monitor mode not working for iwi(4) on 7.X Message-ID: <AANLkTimZD%2B8Ex2FL2cb_Z%2BTOpJV-87Z8xXhLSwtqYWmn@mail.gmail.com> In-Reply-To: <20101006100335.GA26843@FreeBSD.org> References: <4763016D.7060100@janh.de> <20101006100335.GA26843@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 same >> 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 debug > information will be gladly provided. =A0Pointers where to look (revisions > to try, patches, etc.) are greatly appreciated. > > ./danfe > >> iwi_newstate: INIT -> INIT flags 0x0 >> enter FW state 1 >> Setting MAC address to 00:0e:35:91:2b:0b >> sending command idx=3D0 type=3D11 len=3D6 >> Configuring adapter >> sending command idx=3D1 type=3D6 len=3D20 >> Setting power mode to 0 >> sending command idx=3D2 type=3D17 len=3D4 >> Setting RTS threshold to 2346 >> sending command idx=3D3 type=3D15 len=3D4 >> Setting fragmentation threshold to 2346 >> sending command idx=3D4 type=3D16 len=3D4 >> Setting .11bg supported rates (12) >> sending command idx=3D5 type=3D22 len=3D16 >> Setting .11a supported rates (0) >> sending command idx=3D6 type=3D22 len=3D16 >> Setting initialization vector to 3524349664 >> sending command idx=3D7 type=3D34 len=3D4 >> Setting wep key index 0 len 0 >> sending command idx=3D8 type=3D18 len=3D20 >> Setting wep key index 1 len 0 >> sending command idx=3D9 type=3D18 len=3D20 >> Setting wep key index 2 len 0 >> sending command idx=3D10 type=3D18 len=3D20 >> Setting wep key index 3 len 0 >> sending command idx=3D11 type=3D18 len=3D20 >> Enabling adapter >> sending command idx=3D12 type=3D2 len=3D0 >> iwi_newstate: INIT -> RUN flags 0x1 >> iwi_newstate: RUN -> RUN flags 0x1 >> exit FW state 1 >> Setting WME parameters >> sending command idx=3D13 type=3D25 len=3D96 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. 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... -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimZD%2B8Ex2FL2cb_Z%2BTOpJV-87Z8xXhLSwtqYWmn>