linux-kernel - Re: 2.6.29-rc8: Reported regressions from 2.6.28

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b6a2187b0903192220p67880251ue8ba9b392f11da01@mail.gmail.com>
Date:	Fri, 20 Mar 2009 13:20:47 +0800
From:	Jeff Chua <jeff.chua.linux@...il.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Network Development <netdev@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: 2.6.29-rc8: Reported regressions from 2.6.28

On Fri, Mar 20, 2009 at 12:55 PM, Jeff Chua <jeff.chua.linux@...il.com> wrote:
> On Thu, Mar 19, 2009 at 5:38 PM, Johannes Berg
> <johannes@...solutions.net> wrote:
>> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
>>
>>> Ignore the above loop thing. The cause seems to be this one instead.
>>>
>>>
>>> # 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. But
>> I've yet to analyse your data to see why it doesn't in the other case.
>
> Doesn't. Taking away "hiwconfig wlan0 ap auto channel auto" makes it works.

More discoveries...

It seems position of "ifconfig wlan0 up" matters

1) It can't be before iwconfig which will result in "SET failed on
device wlan0 ; Device or resource busy".

2) _Before_ "essid" and "key" settings. "ap auto channel auto" MUST NOT BE SET.

3) _After_ "essid" and "key". Ensure all iwconfig settings comes
before "ifconfig".


So, it seems "ifconfig" must be done as the last stage.

Thanks,
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/