vpn-up/vpn-down missing from ifupdown dispatcher script

[jwm]

Binary package hint: network-manager

The behaviour of non-network-manager managed connections is to trigger the scripts in /etc/network regardless of the interface being brought up or down.

nm, however, has separate vpn-up/vpn-down events for it's dispatcher, and the ifupdown script ignores them. Hence scripts in ifup.d that used to be triggered by an activated tun device no longer work.

Fix:

Where up) -> up|vpn-up)

Same for down. This restores (most of) the old behavior.

[jwm (jwm-angrymonkey)]

True for lucid and earlier, as far as I can tell.

[Mathieu Trudel-Lapierre (cyphermox)]

This still appears to be an issue on later releases, checking whether it should be enabled for VPNs... What would be likely to break if bringing up a vpn was to trigger running ifupdown scripts?

[Mathieu Trudel-Lapierre (cyphermox)]

Marking as a duplicate of bug 661951