[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6a2187b0903190945l29d64016sa755bbd9581968aa@mail.gmail.com>
Date: Fri, 20 Mar 2009 00:45:17 +0800
From: Jeff Chua <jeff.chua.linux@...il.com>
To: "John W. Linville" <linville@...driver.com>
Cc: Frans Pop <elendil@...net.nl>, johannes@...solutions.net,
mingo@...e.hu, torvalds@...ux-foundation.org, rjw@...k.pl,
linux-kernel@...r.kernel.org, bunk@...nel.org,
akpm@...ux-foundation.org, kernel-testers@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: Required sequence to set wireless parameters? (was: 2.6.29-rc8:
Reported regressions from 2.6.28)
On Thu, Mar 19, 2009 at 11:24 PM, John W. Linville
<linville@...driver.com> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists