*** This bug is a duplicate of bug 1754671 ***
https://bugs.launchpad.net/bugs/1754671
** This bug is no longer a duplicate of bug 1688018
DNS server from vpn connection is not being used after network-manager
upgrade to 1.2.6
** This bug has been marked a duplicate of bug 1754671
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
It is impressive how quick there was response and still this and related
bug (#1688018) is abandoned for more than 3 years ...
> On March 23, 2020 3:08:07 AM PDT, Kiruahxh <1671...@bugs.launchpad.net>
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
I'm on 19.10 with a L2TP IPsec connection over wifi
using packages: network-manager-l2tp network-manager-l2tp-gnome
I set both the wifi and VPN IPv4 settings to "addresses only"
When I configure the VPN
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
On March 23, 2020 3:08:07 AM PDT, Kiruahxh <1671...@bugs.launchpad.net> wrote:
>*** This bug is a duplicate of bug 1688018 ***
>https://bugs.launchpad.net/bugs/1688018
>
>It affects me too on Ubuntu
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
It affects me too on Ubuntu 19.04 using OpenConnect VPN
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
This is scary thread for a relatively easy fix, for some reason dnsmasq
and OpenVPN don't play well together, it's as simple as commenting out
the "dns=dnsmasq" line in
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
Affects me on Kubuntu 18.10 too!
Trying the 19.04 release now...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
Using VPN with Ubuntu in countries with censorshop is not possible. This
is a major security issue. How can it be possible, that these bug is
still not fixed yet?
--
You received this bug notification
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
Please fix this. This is a serious security problem for someone like
myself trying to use Linux for work and needing to connect to a VPN on
public networks. I have yet to find a workaround that lets me
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
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
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
This is still not fixed and package 1.2.2-0ubuntu0.16.04.4 has
disappeared from the mirrors :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
I am affected by this bug as well.
* Ubuntu Xenial 16.04 AMD64 w most recent patches
* network-manager 1.2.6-0ubuntu0.16.04.2
* dnsmasq 2.75-1ubuntu0.16.04.4
Goth Queen's comment in post # 15
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
@rouniy @m-witte-d
Hi,
locking down the packages resulted in breaking gdm3 in my installation of
ubuntu-gnome 16.04.4.
That's because gdm3 has a inherited dependency on libnm0 (>=
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
Still not fixed.
Same as @rouniy:
When I lock package version:
sudo apt install network-manager=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm-glib-vpn1=1.2.2-0ubuntu0.16.04.4
sudo apt install
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
** This bug has been marked a duplicate of bug 1688018
DNS server from vpn connection is not being used after network-manager
upgrade to 1.2.6
--
You received this bug notification because you are a
Just did a fresh install of Mint Mate 18.2 onto a new machine. Same
problem exists. While connected to VPN DNS queries are leaking to non-
VPN interface.
This needs to be fixed!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Still not fixed.
So when I lock package version of the:
network-manager (1.2.2-0ubuntu0.16.04.4)
network-manager-openvpn (1.1.93-1ubuntu1)
network-manager-openvpn-gnome (1.1.93-1ubuntu1)
It works again
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** This bug is no longer a duplicate of bug 1639776
name resolution (dnsmasq) fails to send queries out after suspend/resume
reconnects the interface
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
Reopened as #1688018 ... it was requested in #1639776 ... just FYI to
people finding this one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
This bug is marked as duplicate to #1639776 but I think it is not 100%
correct.
I recently updated all packages to latest version and VPN connection is
still not working. Proposed update from #1639776
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** Tags removed: 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.
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
. . and now I can't remove your patched version of dnsmasq-base:
===
# apt remove dnsmasq-base
Reading package lists... Done
Building dependency tree
Reading state
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
Nicholas Stommel (nstommel): your fix didn't work for me. I think I had
the newer version of dnsmasq already, from my distro's repositories, and
Network-Manager 1.2.6 still - even after installing the
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
My work around was deleting the etc/resolv.conf symbolic link and
creating a resolv.conf file with DNS servers of my choice.
However, as mentioned in #13, Disconnect VPN button is missing and
Configure VPN
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
Okay so I have found the issue pertaining to dns resolution on Ubuntu 16.04.2!
There is a critical bug in the package dnsmasq-base here:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776
The
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776
** This bug has been marked a duplicate of bug 1639776
dnsmasq fails to send queries out after suspend disconnects the interface
--
You received this bug notification because you are a member of Ubuntu
Well, scratch that hope and consider me mistaken about Goth Queen's workaround.
It appears that manually setting a fixed DNS server DOES allow for successful
reconnect when the network manager is restarted (whereas before it wouldn't
reconnect period), but just like this bug
Oops, Goth Queen actually provided a solution earlier, it was just difficult
for me to understand at the time. Enter whatever fixed DNS server you want and
set 'Automatic (DHCP) addresses only' under IPv4 Settings in network-manager
for the default network connection. So just manually entering
Okay so since resolvconf and dmasq are not cooperating, I have resorted to
using dnscrypt-proxy. Credit to QkiZ, the dnscrypt-proxy service works EVERY
TIME and ignores the (completely broken) DNS resolution of dnsmasq and
resolvconf. Even with the newest version of network-manager (1.2.6) on
@Mercury
Hi, please note that the change I've made is *only* against the
resolvconf task; as you say and document the issue (and potential fix)
is against dnsmasq; ergo there is no need for a resolvconf patch/change.
You mention:
"and resolvconf was not properly tracking how interfaces were
Ryan,
The problem is not that a recent change in resolvconf caused a
regression.
The problem with resolvconf is that the upgrade to network-manager
exposed an existing bug in resolvconf.
This happens because the new version of network-manager now tells
resolvconf that it must only use a
The change introduced[1] in resolveconf-1.78ubuntu4 over 1.78ubuntu2
affects *when* resolvconf service starts; but does not affect the
runtime code and is not involved in any of the runtime action of the
resolvconf service. I'm marking the resolvconf task as invalid.
If you feel that the
I have downgraded both the network-manager and resolvconf package but I still
experience complete DNS resolution failure randomly, where restarting the
network manager has no effect and I cannot connect to the internet. The only
way to get DNS working again is to completely reboot the computer,
@rooijan : killing the `dnsmasq` process (#16) after connecting to the
VPN works for me (network-manager 1.2.6-0ubunt amd64 on 16.04 lts ).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Maybe if helpful to someone else quickest way for me to work around it
is kill the dnsmasq process. When it restarts itself DNS over VPN is
working.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
This bug also affects our boxes that have network-manager
1.2.6-0ubuntu0.16.0 amd64. Can confirm that one of our boxes, which is
still on 14.04 LTS, and has network-manager 0.9.8.8-0ubuntu7.3 amd64
does not have these issues.
In our case, we noticed that, when VPN is active, network-manager
** Tags added: regression-update
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Aron Xu (happyaron)
** Changed in: resolvconf (Ubuntu)
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Touch
After two and a half weeks, can we please get a build of resolvconf with
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
applied pushed out?
We don't even need the full new release of resolvconf, we just need the
documented bug
** Changed in: resolvconf (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1671606
Title:
DNS server from vpn connection is not
Same issue with openconnect (cisco) and OpenVPN on 16.04.2 LTS.
Connection is established but:
- DNS is not working
- Disconnect VPN button is missing
- Configure VPN is grayed out and not working.
Please either increase priority or allow full downgrade of network
manager. Downgrading
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (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.
Same issue with OpenVPN. As a workaround, once the VPN is connected, I
edit /etc/resolv.conf and add my DNS (nameserver 8.8.8.8).
It makes DNS resolution work again. But if I disconnect and reconnect
the VPN resolv.conf is indeed reseted.
I tried to force my DNS in the VPN settings in the
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1671606
Title:
DNS server from vpn
I have the similar issue, but I'm using OpenVPN and the symptom is
slightly different.
With OpenVPN, the name resolution is normal on the first attempt to
connect VPN (after reboot). However, by disconnect and connect VPN
again, the name resolution will be broken. As below.
== Reproduce steps ==
I've done some additional testing and it seems as though both the
network manager and the resolvconf package need to be downgraded to get
to a working state. If either or both are at the latest revision
(resolvconf = 1.78ubuntu4 and/or network-manager =
1.2.6-0ubuntu0.16.04.1) name resolution
More input...
I downgraded the network manager from 1.2.6-0ubuntu0.16.04.1 to
1.2.2-0ubuntu0.16.04.4. Oddly, name resolution seemed to work for a few
minutes, then resumed the previous behavior where it would use the dhcp
specified DNS.
I downgraded resolvconf from 1.78ubuntu4 to 1.78ubuntu2.
It looks like the resolvconf package was updated on my machine on 3/2/2017
also. Isn't resolvconf responsible for updating DNS info when something like a
DNS lease is obtained?
I'm pretty sure I didn't see the problem until after the network-manager
package was updated around 3/8/2017, but
network-manager:amd64 (1.2.2-0ubuntu0.16.04.4, 1.2.6-0ubuntu0.16.04.1)
I'm seeing a very similar problem, except I'm using a PPTP tunnel. I'm
on a Mint MATE 18.1 distro. On approximately 3/8/2017 the network
manager package was updated and about that time is when name resolution
stopped working
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
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/1671606
Title:
DNS server from vpn
This bug appears to be a duplicate of #167196; can the two reports - and
their 'heat' - be merged?
--
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/1671606
Title:
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.
I can confirm the exact same behavior.
--
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/1671606
Title:
DNS server from vpn connection is not being used after
** Description changed:
I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS.
After recent upgrade of network-manager:amd64 from version
1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution
of VPN's server hostnames does not work. Roll back to version
53 matches
Mail list logo
