From owner-freebsd-net@FreeBSD.ORG Wed Oct 6 17:21:11 2010 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2202E106566C; Wed, 6 Oct 2010 17:21:11 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8506F8FC12; Wed, 6 Oct 2010 17:21:10 +0000 (UTC) Received: by wyb29 with SMTP id 29so7387424wyb.13 for ; Wed, 06 Oct 2010 10:21:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=eUs6PonKCclLm5E51WTz0acVWc/sQC1SlvdhEVLTfa0=; b=IsOlDZM/zfHe9oOL6I3BNQsVa4R0TdA4btQh1utZWCz391rZD3uAwwT6zo+pHIkrHh 6uMM7QbDTdpMNEeIPxodx3rtSq8jbdD5FRzSJBO7o9Yg04YUmu5Aw2jcYxjWHYbvAHdT dTvmPRYDpGZoxYmYqoTsi3mlAuiJX9aOeDR5E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=C3BSgFdGWgqbYwD5nnh8q+69Na1BfDyqy915nY0KzDOQuaP/0L6AeSbud1Xn8eoBnb lIlf+Cyn+trUQMK94B1kdmcXwHU6Ii7TrVcSXeLM4+RyRx1k1Emm4vQ04E1w/3VzUNTq wlLxCXv0wogsz5gwULCQ+38FuQwW+B27bnIIE= MIME-Version: 1.0 Received: by 10.216.2.75 with SMTP id 53mr2427430wee.48.1286384185736; Wed, 06 Oct 2010 09:56:25 -0700 (PDT) Received: by 10.216.133.133 with HTTP; Wed, 6 Oct 2010 09:56:25 -0700 (PDT) In-Reply-To: <20101006100335.GA26843@FreeBSD.org> References: <4763016D.7060100@janh.de> <20101006100335.GA26843@FreeBSD.org> Date: Wed, 6 Oct 2010 11:56:25 -0500 Message-ID: From: Brandon Gooch To: Alexey Dokuchaev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: net@freebsd.org Subject: Re: Monitor mode not working for iwi(4) on 7.X X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2010 17:21:11 -0000 2010/10/6 Alexey Dokuchaev : > 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