I can confirm the udev "critical race": removing /etc/udev/rules.d/85-ifupdown.rules and setting the wireless interface as auto everything works as intended (interface correctly brought up at boot time by /etc/init.d/networking).
I can't explane why udev cannot work correctly even if it uses ifup (as networking init script does); again a suspect: are the 802.11 stack related modules loaded properly before udev starts? I have a modprobe rule (maybe redundant) that loads ieee80211, ieee80211_crypt, ieee80211_crypt_tkip modules together with the ipw2200 one; does udev do the same thing? Or it uses insmod, bypassing modprobe rules?
And, anyway, where is the usefulness of a udev rule that does the same of netbase scripts? I think is better mantaining things as simple as possible... (Debian does it... :) )
I can confirm the udev "critical race": removing /etc/udev/ rules.d/ 85-ifupdown. rules and setting the wireless interface as auto everything works as intended (interface correctly brought up at boot time by /etc/init. d/networking) . crypt_tkip modules together with the ipw2200 one; does udev do the same thing? Or it uses insmod, bypassing modprobe rules?
I can't explane why udev cannot work correctly even if it uses ifup (as networking init script does); again a suspect: are the 802.11 stack related modules loaded properly before udev starts? I have a modprobe rule (maybe redundant) that loads ieee80211, ieee80211_crypt, ieee80211_
And, anyway, where is the usefulness of a udev rule that does the same of netbase scripts? I think is better mantaining things as simple as possible... (Debian does it... :) )