On Friday 11 January 2008 21:27:36 Joachim Breitner wrote: > Hi, > > I also find it quite un-nice to be able to run ifup ath0 to enable > wpa_supplicant, but not ifdown ath0 to stop it. > > Why exactly is is that you can’t provide this functionality? > > Is it because ifupdown insists that it needs some values with manual > method to consider the interface as up? What happens if you use dummy > values there? Or maybe patch ifupdown to have a "none" method that just > runs the hook scripts and doesn’t do anything else?
When ifupdown in unstable supports "-o VAR=$value" on the command line, I can see a fix this bug as being possible. I need some rock solid way to differentiate who called ifdown, the user, or the wpa_cli daemon listening to wpa_supplicant events. ifupdown in experimental supports this. Thanks, Kel.
