Launchpad has imported 26 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=758772.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2015-11-28T12:29:20+00:00 zebul666 wrote:
I am using Ubuntu 15.10 with
- network-manager 1.0.4-0ubuntu5.1
- network-manager-openvpn 0.9.10.0-1ubuntu2
And I configured my ethernet connexion to automatically use my openvpn
vpn setup when connecting.
If I go to dnsleaktest.com, I found out that networkamanager leaks my
dns of my FAI provider and don't use the DNS of the VPN.
However if I close and reopen manually the VPN conenction from
networkmanager applet, the DNS leak does not occur anymore.
So the bug occurs only when the VPN connection is set-up automatically
when login or coming from sleep state. The DNS are not updated to the
ones of the VPN and stays the one previously defined.
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1513437/comments/6
On 2015-11-28T13:02:14+00:00 zebul666 wrote:
no. I was wrong to assume it's because the automatic connection.
Once the connection is up, dns could be ok but leaks 5 minutes later
withtout the connection ever changing !!!
so wtf !
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1513437/comments/7
On 2015-11-28T13:52:56+00:00 zebul666 wrote:
to make things clear, connection uses the LAN DHCP DNS instead of DNS of
the VPN tunnel connection setup by network manager
but it seems heratic
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1513437/comments/8
On 2015-11-29T10:02:53+00:00 zebul666 wrote:
>From the NetworkManager log, it's clear than the previous (before
establishing the VPN connection) DNS settings is retained by dnsmasq and
not removed.
So you end up with 3 DNS servers settings defined in dnsmasq after the
VPN connection is setup, one of which is still the LAN/ISP DNS that
causes the random DNS leak. That DNS entry should have deleted.
I don't know if it's upstream bug or ubuntu. I have opened
https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/1520771 which shows a work-around for the bug
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1513437/comments/9
On 2016-03-11T00:13:56+00:00 Forest wrote:
I have observed this problem as well.
Related:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1513437/comments/10
On 2016-04-05T06:21:35+00:00 Mincho-gaydarov wrote:
I've filled a bug in redhat's bugzilla as I was unable to find this in
the beginning. https://bugzilla.redhat.com/show_bug.cgi?id=1322932
I also experience this problem and it is not limited to NetworkManager
configuration with dnsmaq. This bug appears also when NetworkManager is
managing /etc/resolv.conf directly.
Additional info:
I've tested to deny access to 1-st and 2-nd NS servers from the machine running
OpenVPS server and the result was that the local NS server was used, despite
the fact that the checkbox 'Use this connection only for resources on its
network' is unchecked. This leads to DNS leak if the first 2 NS servers could
not be reached.
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1513437/comments/11
On 2016-04-05T08:36:47+00:00 Thomas Haller wrote:
this DNS issue has some similarities with route-management, where users
want that once VPN connects no traffic is routed via other devices (bug
749376).
NetworkManager currently doesn't understand a concept that activating a
certain connection "vpn0" should prevent DNS/routing via another
connection "eth0". For NM, there are just two connections active, both
have DNS/routing configured (with differing priorities) and such is the
outcome. But the existence/priorities don't affect each other.
As current workaround, you have to ensure that when activating "vpn0" the
untrusted connection "eth0-no-dns" on it's own doesn't provide the conflicting
DNS/routes. Which would for example mean, you cannot specify the VPN gateway
via DNS (because "eth0-no-dns" could not resolve it).
Anyway, this is certainly a valuable feature.
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1513437/comments/12
--
