does not handle VPN connections in dispatcher

[Anand Kumria]

Binary package hint: network-manager

Hi,

Whilst diagnosing a VPN problem, I noticed output from NetworkManager complaining that the script /etc/NetworkManager/dispatcher.d/01ifupdown had exited with status 1.

That only occurs when it is passed an action it does not know how to handle.

With the OpenVPN plugin installed and configured, two actions are passed: 'vpn-up' and 'vpn-down'.

It may be worth handling those two events in a similar manner to how up/down are handled.

Thanks,
Anand

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
IfupdownConfig:
 auto lo
 iface lo inet loopback
Package: network-manager 0.7-0ubuntu1
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
Uname: Linux 2.6.28-7-generic x86_64

[Mattias Eriksson (snaggen)]

I don't know what should be done here for the vpn-* actions, but at least it shouldn't exit with an error code. This caused me some extra time of debuging before I realized that this really wasn't the problem.

[Anand Kumria (wildfire)]

This is relatively easy to fix (just have /etc/NetworkManager/dispatcher.d/01ifupdown handle those two cases) and will reduce frustrating debugging time for everyone.

Thus making the planet a nicer place.

[Brett Delle Grazie (bdellegrazie)]

The attached patch should resolve this issue - it simply adds vpn-up / vpn-down as matching events to up / down. This seems to work quite well on my system, YMMV.

[TheWhiteRaven (porter-jordan)]

Patch confirmed to work for me (although not completely functioning through knetworkmanager). When I try to connect, it will show "activating..." under the VPN connection name. This never changes. I confirmed that the VPN was functional at that time. When I wanted to disconnect, nothing happens. It still shows "activating..." under the connection name. I killed vpnc via a 'sudo killall vpnc' and this shutdown the connection and knetworkmanager showed nothing under the connection name.

This will allow me to get work done via VPN but it is definitely not ideal.

[TheWhiteRaven (porter-jordan)]

However, I do believe that the patch fixed the issue related to this bug.

[Cleber Santz (clebersantz)]

Confirmed in Karmic ( 9.10 ), solved with patch.

[frdu0001 (esl-fdumont)]

Same problem here with
!!! 10.04.1 Lucid amd64 !!!

Patch from Brett Delle Grazie (see above) works!
Thank you very much for you work!

@Ubuntu
Please add the patch to the actual Distribution!

Thank you!

[Leslie Viljoen (leslieviljoen)]

Can this patch please be added to the distribution now? The patch was added in January and the October release of Maverick still does not contain it - what can be done?

[jozefs (selesi+launchpad)]

I can confirm that this affects Ubuntu Maverick and that the included patch resolves the issue.

[Mathieu Trudel-Lapierre (cyphermox)]

This has been uploaded to Natty some time ago; marking Fix Released.

[impedator (impedator)]

My Ubuntu Maverick 64 is also affected. I have applied attached patch and this problem still exists.

To apply patch I have:
1. Download patch and save in to my home folder patch01.txt file
2. Go to /etc/NetworkManager/dispatcher.d
3. execute patch -p0 < /home/folder/patch01.txt

Should I do something more? My 01ifupdown seems to be patched.