Comment 2 for bug 193686

Revision history for this message
pittipatti (pittipatti) wrote :

The command-line which is executed when openvpn gets called is:

/usr/sbin/openvpn --remote routus.ip.addr --ns-cert-type server --nobind --dev tun --proto udp --port 1194 --syslog nm-openvpn --up /usr/lib/network-manager-openvpn/nm-openvpn-service-openvpn-helper --up-restart --persist-key --persist-tun --management 127.0.0.1 1194 --management-query-passwords --secret dev --secret /home/patrick/test.key --ifconfig 192.168.1.222 192.168.1.220

When removing the parameter "--ns-cert-type server" through a wrapper-script to openvpn openvpn starts fine, but the "nm-openvpn-service-openvpn-helper" complains, that it can't pull configuration data:

    May 22 09:19:52 portus nm-openvpn-service-openvpn-helper: <WARNING>^I main (): nm-openvpn-service-openvpn-helper didn't receive a VPN Gateway from openvpn.
    May 22 09:19:52 portus nm-openvpn[13076]: script failed: shell command exited with error status: 1

after removing the "--up" parameter through the wrapper-script, too, openvpn starts fine and the tunnel can be user for quite some sekonds, but then network-manager complains:

    May 22 09:24:04 portus NetworkManager: <WARN> nm_vpn_service_process_signal(): VPN failed for service 'org.freedesktop.NetworkManager.openvpn', signal 'ConnectFailed', with message 'The VPN login failed because the VPN program could not connect to the VPN server.'.

starting openvpn from the command line with the parameters mentioned above (without --ns-cert-type and --up) works fine.