Bugzilla – Bug 112982
wpa_supplicant and ifplugd do not play well together
Last modified: 2007-06-05 10:05:09 UTC
Because wpa_supplicant essentially does not start until the interface tries to do dhcp (or at least it appears that way), ifplugd is useless for wireless cards using ifplugd. Interface just sits there. Found in 9.3, seems the same in 10.0
Yes, it's a known problem.
Anyone know what the priority is on trying to fix it? IMHO, this is a pretty serious issue for laptop users. We all have at least 2 interfaces, and I cannot tell my clients "just open a terminal, switch to root, and run ifup XXX". I can hear the laughing already!
An immediate fix is to set the Wireless interface to "user controlled" and tell them to start it with kinternet. The upcoming fix will be, that wireless interfaces "fake" ifplugd: they always assume "cable plugged in", but have a lower priority than the wired interfaces. So if you unplug the wire, the wireless interface is brought up, regardless if there is an association or not. If you re-plug the cable, the wired interface with its higher priority is preferred over the wireless one and the wireless one is brought down. All the above assumes that you are using "STARTMODE=ifplugd" and not ifplugd standalone. Christian, is this already implemented?
Another possibility is to use scpm.
- When I log in I have to input the WPA key to kinternet. - If the connection is idle for a couple of minutes it disconnects. - If I try to just reconnect to the same connection which I was just on via kinternet it asks for a WPA shared key again. - The key is in the Yast network settings for this interface but kinternet does not seem to pick it up from there. - Had to set the wired eth to manual so that it will work properly. This is on an Asus a6000 Turion 64 Laptop uses Intel 2200BG module (modprobe ipw2200). Connecting to a D-Link DI-624 router with latest firmware. Does not do this running other OS with same hardware.
And of course if you are in a LEAP network, you cannot manually input any keys.
I've modified ifup to not run ifplugd on wlan devices, they are assumed to always have link. This should make it possible to run it together with a higher priorized ethernet interface handled by ifplugd.
Is this in beta4 or perhaps beta5?
beta5 aka RC1 After next sync you will find sysconfig-0.40.5 in ftp.suse.com/pub/people/zoz/sysconfig
Many thanks Christian.