nm-dispatcher.action send wrong argument to scripts

[Volodymyr Palii]

Binary package hint: network-manager

Binary package hint: network-manager-pptp

On Intrepid:

oberon@titania:/$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

With package:oberon@titania:~$ dpkg -S /usr/lib/NetworkManager/nm-dispatcher.action
network-manager: /usr/lib/NetworkManager/nm-dispatcher.action
oberon@titania:~$ apt-cache policy network-manager
network-manager:
  Встановлено: 0.7~~svn20081018t105859-0ubuntu1
  Кандидат: 0.7~~svn20081018t105859-0ubuntu1
  Таблиця версій:
 *** 0.7~~svn20081018t105859-0ubuntu1 0
        500 http://ua.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Scripts in /etc/NetworkManager/dispatcher.d directory needs second argument (action) to be one of these: up, down, pre-up or post-down. But when I establish a connection to VPN server, nm-dispatcher.action set this argument to vpn-up (and to vpn-down on disconnect). As a result, /etc/NetworkManager/dispatcher.d/01ifupdown exit with error, and scripts in /etc/network/if-up.d directory is not started.

[Peter De Maeyer (peter-de-maeyer)]

I'm on Ubuntu 10.04, and this bug has still not been solved. Doesn't seem too hard to fix though...

Use case:
Connect to VPN via the network manager

Symptom:
Connection seems established, but syslog shows error: "nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1."

Cause:
As already mentioned, the script is called with arguments "vpn-up" and "vpn-down" while it expects "up" and "down". Because it does not recognize the arguments "vpn-up"/"vpn-down", it exits with status 1 resulting in the error in syslog.

[Mathieu Trudel-Lapierre (cyphermox)]

This has been fixed in Uubntu Natty if I'm not mistaken. Closing as Fix Released.