I > Hmm, I recently looked to the interaction between rfkill and hal, and > may be able to answer that. The kernel rfkill module also exports its > state via either /dev/rfkill or sysfs's /sys/class/rfkill (depending > on kernel version; I think /dev/rfkill is new to > 2.6.31/wireless-testing/compat-wireless, and not in 2.6.30). hald or > devicekit (again, depend on distro/kernel version) monitors those, and > informs NetworkManager via d-bus messaging when the rkfill state > changes. NetworkManager then if up/down the device and tell > wpa_supplicant accordingly. So the ifconfig-interface-up is supposed > to happen automatically, if hald/devicekit works and talk to > NetworkManager. > > i.e. the waking-up should happen automatically if you have the > combination of hald/devicekit and networkmanager. > > Does this answer your question? > Indeed; it's a good explanation of what's going on. Now I'll follow each step of your descripiton and I'll try to find out where the chain breaks :) Many thanks for your help. -- 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
