From owner-freebsd-current@FreeBSD.ORG Thu Sep 27 00:14:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56E8716A417 for ; Thu, 27 Sep 2007 00:14:08 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from alnrmhc16.comcast.net (alnrmhc16.comcast.net [206.18.177.56]) by mx1.freebsd.org (Postfix) with ESMTP id 1D68E13C448 for ; Thu, 27 Sep 2007 00:14:08 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from antenna.local (c-68-35-224-189.hsd1.fl.comcast.net[68.35.224.189]) by comcast.net (alnrmhc16) with ESMTP id <20070927001407b1600bqhive>; Thu, 27 Sep 2007 00:14:07 +0000 Message-ID: <46FAF5C1.4070106@comcast.net> Date: Wed, 26 Sep 2007 20:13:53 -0400 From: Nathan Lay User-Agent: Thunderbird 2.0.0.6 (X11/20070925) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: iwi oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 00:14:08 -0000 Hi list, With these rc.conf flags ifconfig_iwi0="powersave wme -bgscan" iwi decides to bring itself up on boot. iwi in 6.2 never brought itself unless 'up' was explicitly specified. Though, my 6.2 rc.conf settings are more along the lines of ifconfig_iwi0="wme bmiss 100" Off topic, why the large bmiss? Well, iwi, in both 6.2 and 7.0 (less so in 7.0) decide to have problems with WPA (i.e. sometimes wpa_supplicant 0.4.8 and 0.5.8, will cycle authentication over and over again in short intervals and I'll have to restart wpa_supplicant or reload if_iwi), or iwi will all the sudden disassociates itself from the AP for no apparent reason. I read somewhere a large beacon miss value helps alleviate these problems with iwi. Sometimes when iwi is reset (i.e. due to firmware errors), I am not able to transmit or recieve anything unless I delete the gateway's arp entry even though I am associated and have an IP. I don't think this problem has to do with iwi, but it is annoying to find that I am no longer able to send or receive data out of the blue. This happens regardless of iwi's configuration or load. Anybody experience these iwi oddities? I am pleased to say that iwi doesn't appear to exhibit that annoying DMA error that was present in 6.2. Is there any useful information I can collect? Best Regards, Nathan Lay