Bug#618277: PHASE mismatch in ifupdown script

2011-03-17 Thread Kel Modderman
On Wednesday 16 March 2011 22:19:02 Tormod Volden wrote: > I agree that nowadays this is usually run through dbus and > network-manager and not the ifupdown and /etc/interfaces way, but the > result is the same. Please look at > /etc/NetworkManager/dispatcher.d/01ifupdown - it sets $PHASE and does

Bug#618277: PHASE mismatch in ifupdown script

2011-03-16 Thread Tormod Volden
I agree that nowadays this is usually run through dbus and network-manager and not the ifupdown and /etc/interfaces way, but the result is the same. Please look at /etc/NetworkManager/dispatcher.d/01ifupdown - it sets $PHASE and does run-parts on the corresponding /etc/network/if-XXX.d directory.

Bug#618277: PHASE mismatch in ifupdown script

2011-03-16 Thread Kel Modderman
On Tuesday 15 March 2011 22:24:07 Tormod Volden wrote: > 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 interes

Bug#618277: PHASE mismatch in ifupdown script

2011-03-15 Thread Tormod Volden
Sorry, I messed up the deactivation part in my explanation: It is the "pre-down" clause that never is executed (as hinted by my patch), that is kill_wpa_cli(). That wpa_supplicant was still running, is a different bug/feature (fwiw there is no pid-file). kill_wpa_cli() also depends on a pid-file,

Bug#618277: PHASE mismatch in ifupdown script

2011-03-15 Thread 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.

Bug#618277: PHASE mismatch in ifupdown script

2011-03-15 Thread Kel Modderman
Hi Tormod, On Monday 14 March 2011 08:06:31 Tormod Volden wrote: > Package: wpasupplicant > Version: 0.7.3-1 > > Note that I don't use wpasupplicant so I can not test this, but I > noticed it while studying various ifupdown script. Can you explain what is actually wrong with the shell code I've

Bug#618277: PHASE mismatch in ifupdown script

2011-03-14 Thread Tormod Volden
The easiest way to verify this is to add for instance: logger "$0: $IFACE $ADDRFAM $MODE $PHASE" to /etc/wpa_supplicant/ifupdown.sh and check the output in /var/log/syslog. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact l

Bug#618277: PHASE mismatch in ifupdown script

2011-03-13 Thread Tormod Volden
Package: wpasupplicant Version: 0.7.3-1 Note that I don't use wpasupplicant so I can not test this, but I noticed it while studying various ifupdown script. The /etc/wpa_supplicant/ifupdown.sh is linked in /etc/network/if-up.d so it will be run with PHASE=up and not "post-up". However the script