On Tuesday 08 April 2008 16:05:19 Y Giridhar Appaji Nag wrote: > > This could allow more fine grained policies to the admin, for one example, a > > script could be installed to purposely inhibit the ifupdown action under > > certain conditions. > > The only gripe that I have with this is that if people have scripts that > fail occasionally (because they have action scripts that don't check for > the 'location' they are being run etc.), this may break existing setups. > > Can you give me an example of how one would want to implement policies? > I have a strong suspicion that ifplugd is the wrong place to do this. I > would be inclined to mark this wontfix if that is the case.
I maintain wpasupplicant, and it exposes something similar to ifplugd; a daemon that calls ifup/ifdown on CONNECTED and DISCONNECTED events received from wpa_supplicant control socket. Recently, I started thinking about working on some glue + application, that joins ifplugd + wpa-roam pragma of wpasupplicant together. A reasonable policy to enforce in this case is to have wireless interfaces deactivated when a wired interface is triggering an "up" action via ifplugd. In this case I'd install a script which would communicate to the wpa-roam daemon that a ifplugd up or down event is being triggered, and the wireless state should be toggled. There may be a condition in this use case where the wired interface up action should be ignored. We may be connected to a wireless network that takes priority over any wired network, or the wpa-roam daemon refuses to deactivate and drop its active network connection, in which case the ifplugd ifup action could be terminated. Whether or this is the correct place to make such decisions is up to you; I respect that it may represent a risk to existing setups. I didn't find any scripts installed to ifplugd action.d directory though, apart from the ifupdown script provided by ifplugd itself. I'm just probing to see what kind of flexibility the ifplugd daemon can afford ;-) Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
