Re: openvpn cmdline communication to NM

On Tue, Jun 14, 2016 at 10:57 AM, Thomas Haller wrote: > It would need a more elaborate scheme to report warnings back to the > calling application. I can report that, as an end-user, NM is a complete mystery when anything doesn't work. So +1000 votes for some feedback

Re: openvpn cmdline communication to NM

On Tue, 2016-06-14 at 10:47 -0400, Martin Langhoff wrote: > On Tue, Jun 14, 2016 at 10:33 AM, Thomas Haller > wrote: > > > > Also, import silently ignores unknown values from the file. > > https://git.gnome.org/browse/network-manager-openvpn/tree/propertie > >

Re: openvpn cmdline communication to NM

On Tue, Jun 14, 2016 at 10:33 AM, Thomas Haller wrote: > Also, import silently ignores unknown values from the file. > https://git.gnome.org/browse/network-manager-openvpn/tree/properties/import-export.c?id=96081a2c2e05f64d89433d150053291516bddd5e#n1409 > Maybe that is a bug,

Re: openvpn cmdline communication to NM

On Tue, 2016-06-14 at 08:22 -0400, Martin Langhoff wrote: > Hi Thomas, > > thanks for the explanation. It generally matches my understanding of > the world :-) > > The odd thing is: this is a vanilla client connection, all the > details > are in ovpn file, I am connecting to OpenVPN servers.

Re: openvpn cmdline communication to NM

Hi Thomas, thanks for the explanation. It generally matches my understanding of the world :-) The odd thing is: this is a vanilla client connection, all the details are in ovpn file, I am connecting to OpenVPN servers. Import works, but the connection fails to connect. Debugging it is, um,

Re: openvpn cmdline communication to NM

On Mon, 2016-06-13 at 12:46 -0400, Martin Langhoff wrote: > Hi List! > > is there a practical way to get openvpn commandline to talk to NM to > have NM update resolv.conf with the DNS settings coming from the VPN > endpoint? > > I regularly find in the field openvpn setups which refuse to work >