[pkg-wpa-devel] Bug#618277: PHASE mismatch in ifupdown script

[Tormod Volden]

On Tue, Mar 15, 2011 at 12:46 PM, Kel Modderman wrote:
> Can you explain what is actually wrong with the shell code I've been using for
> a few years, which stops it from functioning as advertised?
>
> I'm not going to be interested enough to consume time investigating a problem
> based on a guess.
>
> Thanks, Kel.
>

Hi Kel,

Yes, by analyzing the code I can say what goes wrong: Upon network
interface activation, the action intended for the "post-up" phase is
not executed (because the script is not in any if-post-up.d directory
- it is linked in the if-up.d directory but $PHASE will here be "up).
The action in question is init_wpa_cli() from functions.sh. This
function only does something if $WPA_ACTION_SCRIPT is set. Therefore
if you personally have been using this code for some years without
WPA_ACTION_SCRIPT set, you would not have experienced any problem.
What the "advertised" use for this is, I do not know. But it is
certainly not working as intended. So I will /guess/ ;) there are
users out there who have problems with their WPA_ACTION_SCRIPT setup.

Upon network deactivation, for the same reasons, kill_wpa_supplicant()
is not run. This I can verify myself even without using WPA: 1. See
that there is a running /sbin/wpa_supplicant process. 2. Deactivate
networking for instance with nm-applet. 3. See that
/sbin/wpa_supplicant, against intended behaviour, is still running and
has therefore not been killed by kill_wpa_supplicant() . In case you
added that logger line, you can see how the ifupdown script is called.
This is not a guess :)