Required sequence to set wireless parameters? (was: 2.6.29-rc8: Reported regressions from 2.6.28)

Frans Pop
2009-03-19T15:02:56Z

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. But
>> I've yet to analyse your data to see why it doesn't in the other case.
>
> That is what I was going to suggest. I go so far as to say that you
> should set everything else before doing the "iwconfig wlan0 essid
> xxx" bit.

Mostly just curious, but is that actually required by some wireless
standard? If not, is it really reasonable to ask userland to do things in
that particular order?

Reason I ask is that for example when writing wireless support for e.g. a
distro installation system, it seems most logical to *first* ask the user
what network (ESSID) he wants to connect to. Next to check if we can
connect to that network without additional authentication and only then,
if needed, ask for keys etc.
If it's not possible to set that info in that logical order that seems
rather restrictive to me and would probably mean that you'd have to reset
AP, ESSID and possibly other settings before each incremental attempt.

Cheers,
FJP