On Mon, Mar 24, 2008 at 12:28:07AM +0200, Tomas Winkler wrote: > Why should be possible to configure device when it's not up. Shouldn't > be there some order in which things are happening? I don't know if it should be possible, but the debian ifup scripts seem to do it that way. I just configured the interface in /etc/network/interfaces using the wireless_* config options, and 'ifup wlan0' fails to start the network as the interface doesn't associate. It does work if I manually call 'iwconfig wlan0 ap any' after the scripts brought the interface up. With the patch, 'ifup wlan0' works perfectly for me. Also, I'm not the only one with this problem, as I found exactly the same hint with google: http://bayleshanks.com/tips-computer-lenovoX61t-gnuLinuxSetup "I found that I have to do "iwconfig wlan0 ap any" before it will associate with my router. Dunno if that's a general problem or if I did something wrong in /etc/network/interfaces." (Please not that I'm using a Lenovo x61s, and the mentioned link talks about an x61t, which are quite similar. So it may be that this behaviour is only visible with some hardware configurations.) Jan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
