Comment 8 for bug 259562

Downgraded to openvpn 2.1~rc7-1ubuntu3, and it is again possible to connect to the VPN (and with LZO enabled, I can actually use the tunnel as well). However, the default route is _not_ redirected to go over the VPN tunnel like it was in NM 0.6 (my IPv4 settings method is "Automatic (VPN)"), I need to manually fix it in order for the VPN tunnel to be used.

The last line that is printed to syslog after activating the connection might give a clue why:

Aug 20 00:00:17 envy nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.

However, this bug might very well be fixed by openvpn 2.1~rc8, so we can put it on hold for a while. When I upgrade to 2.1~rc8 again, I get the same error message as before, and the connection fails completely:

Aug 20 00:08:34 envy nm-openvpn[22284]: /usr/lib/network-manager-openvpn/nm-openvpn-service-openvpn-helper tun0 1500 1542 10.8.0.6 10.8.0.5 init
Aug 20 00:08:34 envy nm-openvpn[22284]: openvpn_execve: external program may not be called due to setting of --script-security level
Aug 20 00:08:34 envy nm-openvpn[22284]: script failed: external program fork failed
Aug 20 00:08:34 envy nm-openvpn[22284]: Exiting

I'll update the title of this bug to indicate that this is the problem at the moment.

Tore