On Tue, 2016-07-19 at 16:46 +0200, Xen wrote: > A user reported having two dhcp-option in his config, either pushed > by > the server or local, I don't know yet. > > One of the dhcp-option was faulty, it was 10.8.0.1 but there was no > response from that server apparently. > > The order given was: > > public internet DNS > private VPN DNS > > In the log from NetworkManager only the second one shows up as being > added to DNSmasq via dbus. As a consequence, since the local > resolv.conf > points to 127.0.1.1, his names do not resolve. > > Using OpenVPN directly caused the connection to succeed as normal > with > two elements written to /etc/resolv.conf apparently. Using OpenVPN > through NetworkManager caused the above described behaviour. > > Is this correct behaviour, a bug, or a lacking feature? I'm trying > to > have him change his VPN config, but I cannot influence what > NetworkManager is going to do, myself. > > Version of NM is probably going to be around 1.2.0.
Can you get debug information out of the nm-openvpn-service process for the attempt? We need to see what openvpn is sending to NM. You can do this by: killall -TERM nm-openvpn-service /path/to/nm-openvpn-service --debug --persist (path will be different depending on your distro, like /usr/libexec or /usr/lib or whatever LIBEXECDIR is defined as during the build) and then connect the VPN. A lot of information will be dumped to the terminal here, *INCLUDING PASSWORDS* so please strip those out before sending. Dan _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
