On Wed, Jan 16, 2008 at 08:22:19PM +0000, Simon Huggins wrote: > Is it still true that there are drivers that don't want the interface to > be up?
Yes, but I think they're in the minority now, especially now that there is a generic 802.11 stack in the kernel. > I can't ifup wlan0 successfully on my laptop (iwl4965) now without > adding > up iwconfig wlan0 essid <blah> > to each stanza which seems a bit wrong. > > I thought this was a kernel bug but here is the response I got: > http://bugzilla.kernel.org/show_bug.cgi?id=9764 Well the maintainer of the wireless extensions in the kernel has said that commands like "iwconfig eth0 essid ..." should never result in an error, it is just a way for the user of saying "when you associate, do it with this SSID". However the kernel driver maintainers apparently disagree, and some drivers associate when doing iwconfig essid, for which the interface must be up, other drivers associate when doing ifconfig up, for which you have to do the iwconfig essid part before the interface is up. Of course, the proper way would be to accept and remember the essid set when the interface is down, and associate when the interface is brought up, and when you change the essid when the interface is still up, reassociate. Maybe I'll change the pre-up script to a post-up script, but I'm sure I'll get bug reports from other people then. In the mean time I think I'll start a discussion with the kernel driver maintainers and see if we can come to a working solution. -- Met vriendelijke groet / with kind regards, Guus Sliepen <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
