Bug 112982

Summary:	wpa_supplicant and ifplugd do not play well together
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Jonathon Robison <jrobiso2>
Component:	Mobile Devices	Assignee:	Joachim Gleissner <joachim.gleissner>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	fdalmoro
Version:	Beta 3
Target Milestone:	---
Hardware:	i586
OS:	All
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jonathon Robison 2005-08-25 13:40:26 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

Comment 1 Joachim Gleissner 2005-08-25 14:22:06 UTC

Yes, it's a known problem.

Comment 2 Jonathon Robison 2005-08-25 14:31:50 UTC

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!

Comment 3 Forgotten User ZhJd0F0L3x 2005-08-26 09:24:56 UTC

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?

Comment 4 Joachim Gleissner 2005-08-26 09:51:44 UTC

Another possibility is to use scpm.

Comment 5 Fernando Dal Moro 2005-08-28 05:04:50 UTC

- 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.

Comment 6 Jonathon Robison 2005-08-29 13:19:42 UTC

And of course if you are in a LEAP network, you cannot manually input any keys.

Comment 7 Joachim Gleissner 2005-09-02 12:51:06 UTC

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.

Comment 8 Jonathon Robison 2005-09-02 12:55:11 UTC

Is this in beta4 or perhaps beta5?

Comment 9 Christian Zoz 2005-09-02 13:04:28 UTC

beta5 aka RC1

After next sync you will find sysconfig-0.40.5 in
ftp.suse.com/pub/people/zoz/sysconfig

Comment 10 Jonathon Robison 2005-09-02 13:10:01 UTC

Many thanks Christian.