*** This bug is a duplicate of bug 1754671 ***
https://bugs.launchpad.net/bugs/1754671
** This bug has been marked a duplicate of bug 1754671
Full-tunnel VPN DNS leakage regression
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Ah, I forgot to mention I've found a somewhat working workaround. If you
uncomment the line "DNS" in /etc/systemd/resolved.conf and put list of
DNSes with first VPN's DNS then your normal DNS, then it will always try
to go through the VPN's DNS first even if you're not trying to access a
resource
I'm on Ubuntu 20.04 and I've tried every solution listed above and in
the bug's duplicate and none of them worked... It's really disappointing
that dns doesn't work with VPNs for over 4 years.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Tags removed: sts-sponsor-volunteer
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn connection is not
** Changed in: network-manager (Ubuntu Xenial)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
** Changed in: network-manager (Ubuntu Yakkety)
Assignee: Mathieu
** Tags added: sts-sponsor-volunteer
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn connection is not being used after
The silence regarding this problem is a bit disconcerting. After jumping
through many hoops, I managed to resolve this with the help of this
answer: https://forum.manjaro.org/t/weird-dns-issue-over-vpn/78092/11
I deleted the /etc/resolv.conf symlink and disabled systemd-resolved as
instructed,
> I'm also effected by this bug on 18.04.3 (NetworkManager v1.10.14)
please note that n-m version 1.10.14 never was released out of Bionic-
proposed; instead smaller fixes were used to address specific bugs, and
the latest NetworkManager version in Bionic-updates is
1.10.6-2ubuntu1.2. If you
Hi!
@Vadym K (hmvs): What is your workaround good for?
In general:
I'm also effected by this bug on 18.04.3 (NetworkManager v1.10.14) and can't
see any 'official' solution (for Bionic). – Can someone maybe help (me)?
Thanks and KR!
--
You received this bug notification because you are a
18.04.3 LTS !, still reproduced, which makes me sad.
As a workaround: `sudo apt-get install resolvconf-admin`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
On 19.04 I can see the following (correct) behavior.
With VPN (turned on via NetworkManager):
# note: no "global" DNS servers have been configured by hand through
systemd-resolved conf using "DNS=" directive
systemd-resolved --status
# ...
Link 15 (tun0)
Current Scopes: DNS
DefaultRoute
** Changed in: network-manager (Ubuntu)
Milestone: ubuntu-17.06 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn
This bug and the fact that there seems to be no care in fixing it made
me leave the Ubuntu distro behind. Pathetic. I no longer care if you fix
it or not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn connection is not being used after
The author discusses the drawbacks here: https://github.com/jonathanio
/update-systemd-resolved (one can still leak under certain
circumstances, and we shouldn't only be concerned with the minority who
realize this is even happening/a problem and who can hack together a
workaround themselves). Not
For those using OpenVPN, I discovered that there is a package named
'openvpn-systemd-resolvd' that finally resolved this issue for me.
Here's the synopsis for the package in the repo...
"This is a helper script designed to integrate OpenVPN with the
systemd-resolved service via DBus instead of
This is the *nastiest* bug I've ever encountered in the wild on my own
in Linux (that has no good solution after this long). Package
1.2.2-0ubuntu0.16.04.4 has disappeared from the mirrors for Xenial (not
that anyone should expect a normal user to go through the deep dive that
is this subject,
Thanx Colin.
Anyway anyone knows why this bug is sooo hard to fix? It is old, and quite
blocking someones workflow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
It has only been marked Won't Fix in Yakkety, because Yakkety is well
past it's sell by date. It is still open on Xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Sebastien, could you explain the 'status: Triaged → Won't Fix' meaning?
Is this bug going to stay with us or what?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Changed in: network-manager (Ubuntu Yakkety)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from
I am running Ubuntu 16.04 with plasma. I was experiencing this issue and
downgraded the network-manager package to 1.2.2-0ubuntu0.16.04.4. Since
the downgrade I haven't had any trouble. Waiting for fix in the latest
version :)
--
You received this bug notification because you are a member of
This problem:
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1688018/comments/18
remains and now the old package 1.2.2-0ubuntu0.16.04.4 is not available
anymore. Can we go back to the behaviour of 1.2.2-0ubuntu0.16.04.4 ?
--
You received this bug notification because you are a
I'm experiencing this issue on Ubuntu 18.04.1. In case this helps
anyone, I've been able to fix following
https://wiki.archlinux.org/index.php/OpenVPN#Update_systemd-
resolved_script. Only after that change the OpenVPN supplied DNS servers
appear on `systemd-resolve --status`. In case that
Thanks Egor! Connection stayed up all day!!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn connection is not being used after
Well, that was pretty straightforward! Thanks for pointing that one out,
we'll know in a couple hours if it worked.
Peace & Joy; Love & Gratitude
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
@hckrmagoo I had this problem as well, try making NetworkManager run
OpenVPN as root: https://askubuntu.com/a/906055/844205.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
THank you Egor! that did the trick on Kubuntu 18.04. Now if I could only
figure out why it disconnects from the VPN after .5-2 hours...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
@egor-tensin you are awesome! I think there might be a few related
problems (like https://github.com/systemd/systemd/issues/7182) but this
seems to actually work. I actually saw this bug but didn't click that
your fix would work until having wasted a huge amount of time.
Some one from Ubuntu
Thank you @egor-tensin! I've been struggling with this problem for
years. This is the first work around that actually works! I added that
line under the [ipv4] section of my VPN connection file and then
restarted the network manager with:
sudo systemctl restart NetworkManager.service
Now it's
@egor-tensin Thanks. Your walk-around works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn connection is not being used after
> Comment here only if you think the duplicate status is wrong.
Or I won't.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn
I had a lot of trouble with NetworkManager+OpenVPN on Ubuntu and
discovered a couple of workarounds.
If you're having trouble resolving internal domain names (like
*.internal.company.com), you might want to try adding something like
this to the [ipv4] section in /etc/NetworkManager/system-
Commenting out dnsmasq stopped working. What I have done recently:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
so my kernel is 4.13 and to my big surprise after connecting with OpenVPN I can
resolve host names of my remote site (using host myhost.remote.domain.name),
but I cannot ping to
This bug forced me to search for ubuntu alternatives. I'm looking
currently at Manjaro.
About commenting out dns=dnsmasq.
Doing so on laptop (LAN and wifi connections active) has this drawback:
ping my_comp_name
.unresloved name
adding my_comp_name to /etc/hosts makes the ping my_comp_name
What happened to this bug? Is it still being addressed? I'm also experiencing
the same problem and the solutions above don't work for me :(
Ubuntu 16.04.4 LTS
NetworkManager 1.2.6
dnsmasq 2.76
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Almost year old bug still there. This is core functionality of any OS
(secure VPNs, DNS) which just does not work on Ubuntu. I don't know how
about other distros but I doubt that Ubuntu can claim to be the desktop
system with such a bug.
I can confirm that the simplest workaround is comment out
The script in #37 didn't work for me, as the interface name was "tun0".
The following slightly modified script seems to work OK so far:
# cat 99-openconnect-dnsmasq-bug
#!/bin/bash
set -e
# force restart of dnsmasq on vpn connect
# See
By far, the easiest and most effective workaround I've found is commenting out
"dns=dnsmasq" in "/etc/NetworkManager/NetworkManager.conf" as a few others have
suggested above.
Disappointing that this continues to be an ongoing problem.
--
You received this bug notification because you are a
Will the fix also ensure that the search domain of the VPN's DHCP server
will be used?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server
I found another workaround, that works fine without changing package versions
or DNS servers.
It is tested with the issues I had with openconnect for NM.
it is "just" killing the dnsmasq instance and it gets restarted
automatically which then results in a working system again. It easy and
not
This workaround is not bad indeed and saves me, too. But it has
drawbacks that people need to know
1) In newer Ubuntu versions, "dnsmasq" is the default DNS option, so the
config does not have this option to comment out. Instead you have to set
"dns=default" there.
2) With this workaround, some
As a workaround, I commented out dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf.
Now network manager adds VPN DNS servers to /etc/resolv.conf and everything
works as expected.
As an additional benefit, it also adds and uses additional search domains but
only with "Use this connection
I have exactly the same Problem like User Orange Shiang-Yuan Kao
(orange-kao) wrote on 2017-03-22 in Comment #10 in duplicate Bug 1671606
since upgrading to
Kubuntu 17.10
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1671606/comments/10
--
You received this bug notification
... and my issue is now resolved in Ubuntu 17.10, at least on a fresh
install. Not sure what changed, but no changes are necessary to
/etc/nsswitch.conf in order to make resolving DNS work with internal
domains while connect to openconnect VPN. Probably I should stick with
LTS :-)
--
You
@jsseidel I believe starting from 16.10 ubuntu use systemd-resolved as
dns. Your issues might come from that and it would explain why it's also
present in Fedora 25
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I don't know if my issue is related to this or the few others I've seen,
so I pre-apologize if this should be moved elsewhere or even if it's not
relevant in this context. I'm far from an expert in DNS . . .
My experience was that after upgrading to 16.10 (or higher: it happens
in 17.10, too, and
I wonder how many people's DNS leaked over the year this bug hasn't been
addressed. Oh well..it's just your users' security. Canonical is a joke.
Please stop endangering your users with your incompetence.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@cyphermox please comment on the status Mathieu.
Still using the workaround: https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1671606
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
@joll-nicholas I just want to add my view of this situation to this bug
report. :) It was more like message to all in this thread ... my
apologize if it was not written properly (I am not native speaker)
@kantlivelong ... yeah, for now (I mentioned this also in initial
report) but it may not be
On my Mint (18.2 and I think I did it on 18.3 too - both Cinnamon) the
network-manager downgrade sufficed; I did not need to adjust resolvconf.
However, I don't think I was using a 'PPTP tunnel'.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Just an FYI, I have to downgrade both network-manager=1.2.2-0ubuntu0.16.04.4
and resolvconf=1.78ubuntu2. Doing one or the other would not fix the problem
on my system (Linux Mint Mate 18.1).
I'm using a PPTP tunnel.
--
You received this bug notification because you are a member of Ubuntu
Just downgrade network-manager to 1.2.2-0ubuntu0.16.04.4 until the issue
is resolved. Pretty simple.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
@lukas-d: I understand, but perhaps you are thinking that I work for
Canonical or that I have the skill to contribute to the network-manager
project. Neither of those things are true. I am a frustrated user (with
fairly low programming ability).
It seems to me that switching to a distribution
@joll-nicholas ... "it is not guaranteed secure." ... Explain this to
employer. I am using VPN as it is requirement of my employer. They don't
care if it work or not on Linux. M$ Windows client is working and that
its. We are not in position to negotiate VPN solution especially if it
is not
@terry69lawson and other frustrated users: perhaps you are in a position
to try *WireGuard* as a replacement for OpenVPN (or for other methods of
connecting to a VPN). Your VPN provider will need to have WireGuard
servers for this to work. If your provider does have such servers, then
you are in
Now NONE of my Ubuntu machines, on Xenial or Zesty, will use my VPN for
even a brief time. I've tried several different versions of packages,
but nothing. This is absolutely intolerable. Fix this soon Canonical or
I will be forced to leave for a different Linux distro.
--
You received this bug
I hope this bug will be fixed soon for 16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn connection is not being used after
Using a VPN I have at hand (I don't control the server part of it, though), I
can confirm that with n-m 1.2.6 my local DNS (10.0.5.5) is injected after the
vpn is established:
Aug 31 20:36:32 31-64 dnsmasq[1118]: setting upstream servers from DBus
Aug 31 20:36:32 31-64 dnsmasq[1118]: using
Oh, that box is on xenial, btw.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn connection is not being used after
Corrections to the above post.
(i) '[I]t its original' should be 'in its original'.
(ii) 'Inference from the conjunction of 1, 2 and 3' should be,
'Inference from the conjunction of 1, 2, 3 and 4' - because I found
another reason.
A facility to edit posts would be welcome (but perhaps that
1. It has been four months since this bug - it its original incarnation
(https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606)
- was reported.
2. The bug is critical: it breaks security software.
3. The bug has been reported to Ubuntu, which has paid employees.
4. The bug is a
Any updates? It would be nice to see full closure on this issue ASAP.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
DNS server from vpn connection
Cruz, thanks for this.
However, (1) after all the trouble I had getting OpenVPN working, I
don't fancy switching to something else (and my system does work at
present, using the older version of Network Manager).
Also, (2) I don't really understand what you say about /etc/hosts,
though probably
Just expanding a little bit more my last comment, on Ubuntu 17.04, using
the 'sudo openconnect xxx' command is adding to the file
/run/resolvconf/resolv.conf file the DNS IP addresses as global ones.
Just also added them on the 'icon' version and it fixed it too. In
Ubuntu 17.04 it's using by
On my Ubuntu 17.04 (also happened on 16.10, upgraded to 17.10 that same
machine) the bug it's happening to me. My current workaround is to use
an equivalent 'openconnect'.
Command issued in my case:
sudo openconnect --user my-vpn-user --csd-user my-local-unix-user
--csd-wrapper
Might I ask when this rather severe bug is due to be fixed (in Xenial or
rather, for me, in Mint)? Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
I am glad to see that this bug is being worked on and is rightly
labelled as being of high importance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1688018
Title:
I experience the same issue on 16.04 but it ends up breaking DNS
responses entirely because traffic is forced through the OpenVPN tunnel
where the DNS resides and the local DNS is no longer accessible.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I don't know what your "DNS leak test" is, but we can't give much weight
to that unless we also know a lot more about your config for the VPN and
how the test is set up, what it looks for, etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I'm running on Ubuntu GNOME 17.04 and I'm still affected by this issue.
After connecting to VPN and running a DNS leak test, it still shows my
DNS as my usual ISP.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Has anyone tried to make their connections with an even newer version of
Ubuntu and network-manager, such as on 17.04? That would be a very good
test to do (in my experience, it works correctly).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I don't know why bugs about "DNS on VPN" were being marked as duplicates
of suspend/resume issues in dnsmasq. It's /related/, but definitely not
the same thing at all. I can only apologize that this wasn't handled
correctly, and try to fix things.
One thing to keep in mind however, is that not
Seumas: It seems that Canonical simply don't care about VPN users. This
is opened for more than two months and still not reasonable response :(
...
... right now there is only one workaround:
- downgrade network manager:
apt-get install network-manager=1.2.2-0ubuntu0.16.04.4
- set it on hold
Seumas: since Canonical seem to be dragging their feet on this, you
might as well downgrade to network-manager 1.2.2, which is a version
that works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
For weeks now my only workaround for this problem has been to run a
terminal script to connect and disconnect the VPN every 20 minutes. This
is very inconvenient and impractical for things which require
uninterrupted network traffic, so I hope a permanent fix is released
ASAP.
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
77 matches
Mail list logo
