Whether this is a bug or feature request, I don't know, but to be sure, it is possible to do this with a .conf file and "sudo service openvpn start" and not possible to do it via network-manager-openvpn (unless you count disabling dnsmasq--I'm curious what side effects this has). As described in the original report, I have verified that these lines in a .conf file allow the server to configure DNS (as long as the server pushes 3 or more DNS servers):
script-security 2
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf
but network-manager-openvpn does not support the 'up' and 'down'.
Whether this is a bug or feature request, I don't know, but to be sure, it is possible to do this with a .conf file and "sudo service openvpn start" and not possible to do it via network- manager- openvpn (unless you count disabling dnsmasq--I'm curious what side effects this has). As described in the original report, I have verified that these lines in a .conf file allow the server to configure DNS (as long as the server pushes 3 or more DNS servers):
script-security 2 update- resolv- conf update- resolv- conf
up /etc/openvpn/
down /etc/openvpn/
but network- manager- openvpn does not support the 'up' and 'down'.
This same issue was addressed here:
http:// askubuntu. com/questions/ 519920/ how-to- run-an- up-script- using-network- manager- openvpn