From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Chua Subject: Re: Required sequence to set wireless parameters? (was: 2.6.29-rc8: Reported regressions from 2.6.28) Date: Fri, 20 Mar 2009 00:45:17 +0800 Message-ID: References: <1237143683.24621.7.camel@johannes.local> <20090315202603.GA9077@elte.hu> <1237317742.31814.28.camel@johannes.local> <1237455534.5100.56.camel@johannes.local> <20090319141311.GA3587@tuxdriver.com> <200903191602.58790.elendil@planet.nl> <20090319152441.GB3587@tuxdriver.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tRIO9mPOGB4u+M629TtXNRjMq5nN2wQAkvNMUuF4j7Y=; b=TjpRtRdxNEnr7oKhV6LDMHdndWnUeluDf5sbWu0rtWm4mCXKfRQej9z9UaQS2xQma0 fXx/lxJeWr5kjbdF/xE+dGAROA9qAOinlUpaW/SUtDJ/tdafoSIdwdH5GmQqzHO94zW5 a5eP62GNcHdx1Y8CS0DJLaOOCaDeuUcf+lPtk= In-Reply-To: <20090319152441.GB3587@tuxdriver.com> Sender: netdev-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: "John W. Linville" Cc: Frans Pop , johannes@sipsolutions.net, mingo@elte.hu, torvalds@linux-foundation.org, rjw@sisk.pl, linux-kernel@vger.kernel.org, bunk@kernel.org, akpm@linux-foundation.org, kernel-testers@vger.kernel.org, netdev@vger.kernel.org On Thu, Mar 19, 2009 at 11:24 PM, John W. Linville wrote: > On Thu, Mar 19, 2009 at 04:02:56PM +0100, Frans Pop wrote: >> John W. Linville wrote: >> > On Thu, Mar 19, 2009 at 10:38:54AM +0100, Johannes Berg wrote: >> >> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote: >> >> > # this needs patch to work ... >> >> > iwconfig wlan0 mode Managed >> >> > ifconfig wlan0 up >> >> > iwconfig wlan0 essid xxx >> >> > iwconfig wlan0 key restricted xxx >> >> > iwconfig wlan0 ap auto channel auto >> >> >> >> If you swap the key and essid lines, it will probably always work. I just discovered that "iwconfig wlan0 ap auto channel auto" is the one causing the problem on 2.6.29-rc8. Remove the line and it'll associate to the AP. Just tried on two different APs a few times, and it seems to behave that way. If I execute the "auto" command, it'll fail to associate, but works fine with the patch. Jeff.