** No longer affects: network-manager (Ubuntu Yakkety)
** No longer affects: network-manager (Ubuntu Xenial)
** No longer affects: network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@litinoveweedle this bug is marked fixed. If you are still seeing a
similar symptom then I suggest opening a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
name resolution
Any updates for this one? After half year? on LTS? Are you serious?
Please note, that this bug #1672491 , ##1639776 and many other could be easily
patched, just by applying patches:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
Have the same issue on 17.04
In order to make dns resolution work again one should type after resume:
sudo systemctl restart systemd-resolved.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, just noticed this is likely the same patch merged here -- well, I'm
running the latest Xenial packages:
ii dnsmasq-base2.75-1ubuntu0.16.04.1
amd64Small caching DNS proxy and DHCP/TFTP server
ii network-manager
Hmm, just noticed this is likely the same patch merged here -- well, I'm
running the latest Xenial packages:
ii dnsmasq-base2.75-1ubuntu0.16.04.1
amd64Small caching DNS proxy and DHCP/TFTP server
ii network-manager
FWIW I continue to face this issue specifically when suspending while
using the mobile broadband connection(predictable interface name
wwp0s29u1u4i6) on my x220. I noticed this thread:
https://mail.gnome.org/archives/networkmanager-
list/2016-September/msg0.html
Which notes this command is
Here is bug report for DNS VPN problems -> #1688018 ... as requested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
name resolution (dnsmasq) fails to send queries out after
@exander77 there is no need for personal abuse here. In that case the
description of this bug should have been updated to include that.
However I see there is debate on that bug about whether it is fixed by
the version of dnsmasq which fixes this bug. If not then it is
definitely a different bug.
@colin-law That's bullshit, #1671606 was closed as duplicated of this:
DNS server from vpn connection is not being used after network-manager upgrade
to 1.2.6-0ubuntu0.16.04.1
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606
--
You received this bug notification because
@exander77 this bug is specifically about a failure after
suspend/resume. If your issue does not relate to suspend/resume it is a
different bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
I did some testing, it affects PPTP, but does not seem to affect
OpenVPN.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
name resolution (dnsmasq) fails to send queries out after
I have a fully updated Ubuntu 17.04 and when I connect to VPN
/var/run/NetworkManager/resolv.conf does not get updated with DNS. Any
fix soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Paul, Nish ... VPN problem was initially reported as #1671606 . This bug
get closed as duplicate to this one. I am not against opening new bug
but we need some kind of statement "why?" ... I don't want to open bug
which may get duplicated again to this one.
I will test proposal from Paul to see
Ah yes. This is indeed referenced in the changelog on the system.
Not sure what I should do next though. Open a new bugid or continue
here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Yes, that version is OK (I'm on 16.10 so mine is a bit newer). If you
check /usr/share/doc/dnsmasq-base/changelog.Debian.gz on your system you
should see info related to this bug in that changelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Paul
dnsmasq is 2.75-1ubuntu0.16.04.2 and I don't see anything newer within
my repo. Has the pkg been updated for 16.04?
pkg info:
https://pastebin.com/aximAJxc
Mint 18.1 (Ubuntu 16.04.2) x64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Shawn B it sounds like your issue might be related to this one, since
it's fixed by restarting dnsmasq. Do you have the newer dnsmasq version
(you need dnsmasq-base 2.76-4ubuntu0.1 or better)?
Just to note: it's definitely true that this bug will impact VPN users;
that's how I ran into it.
** Changed in: dnsmasq (Ubuntu Xenial)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: dnsmasq (Ubuntu Yakkety)
Assignee: Nish Aravamudan (nacc) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Lukas, thank you for the detailed information. However
On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while
It sounds like a different bug to me, if changing networkmanager fixes
it without changing dnsmasq. I would file a new Launchpad bug with all
the details you can provide. You can add a comment to this issue with a
link.
In particular, please specify:
* If you're using IPv4 vs. IPv6
* If you
Lukas, thank you for the detailed information. However
On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while
I also have the same issue as Lukas.
Occurs:
VPN Connects using redirect gateway
VPN DNS is not used
Local DNS unavailable
No DNS queries work
Expected:
VPN Connects using redirect gateway
VPN DNS is used
Local DNS unavailable
Temporary workaround:
sudo pkill dnsmasq
--
You
Hello Paul. DNS leak mean that DNS queries still hit local DNS server
while VPN connection is active. DNS resolver should query only DNS
servers defined by VPN while connection is active.
I did following test:
- upgraded network-manager to 1.2.6-0ubuntu0.16.04.1
I think the problems being reported by NJ and Lukas at least, are
different issues and you should file a new report about them. I can't
say about GammaPoint because the description there ("DNS leaks") is not
understandable to me.
This issue has the following characteristics: DNS lookups fail,
I am running Ubuntu 16.04.2 LTS and I updated all packages to latest
stable version including dnsmasq-base (2.75-1ubuntu0.16.04.2). VPN
connection is still not working. Wireshark show that all queries are
forwarded to local DNS server instead of one defined by VPN. This is not
only information
This bug fix corrected my VPN leaks in Ubuntu 16.10, but I've since
upgraded to 17.04 (fresh install) and I'm seeing DNS leaks again. Should
this issue be fixed in Zesty already, or is that coming later?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've installed dnsmasq-base_2.75-1ubuntu0.16.04.2 (on Linux Mint),
installed the 1.2.6 version of Network Manager and . . my VPN still
didn't work; the problem (that I had with network-manager 1.2.6 and the
older version of dnsmasq) wasn't solved. Still, my problem didn't begin
after
This bug was fixed in the package dnsmasq - 2.75-1ubuntu0.16.04.2
---
dnsmasq (2.75-1ubuntu0.16.04.2) xenial; urgency=medium
* Add two upstream patches to fix binding to an interface being
destroyed and recreated. LP: #1639776.
+ 2675f2061525bc954be14988d64384b74aa7bf8b
This bug was fixed in the package dnsmasq - 2.76-4ubuntu0.1
---
dnsmasq (2.76-4ubuntu0.1) yakkety; urgency=medium
* Add two upstream patches to fix binding to an interface being
destroyed and recreated. LP: #1639776.
+ 2675f2061525bc954be14988d64384b74aa7bf8b
+
Hi Paul,
https://wiki.ubuntu.com/StableReleaseUpdates is the standard reference.
It takes at least 7 days in -proposed before the SRU team will release
it.
Thanks,
Nish
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Hi Paul,
https://wiki.ubuntu.com/StableReleaseUpdates is the standard reference.
It takes at least 7 days in -proposed before the SRU team will release
it.
Thanks,
Nish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Given the current state of Zesty and the proximity to a release day I
believe we need patience here heh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
name resolution (dnsmasq) fails
Just curious if there's more work needed here before this fix moves out
of proposed and into standard updates for xenial / yakkety, or if not
then is there a timeline when that transition is normally expected?
I'm currently recommending to users that they reset NetworkManager by
hand when they
I have merged in another bug(s) and updated the name of the bug to be a
bit more "user friendly".
** Summary changed:
- dnsmasq fails to send queries out after suspend disconnects the interface
+ name resolution (dnsmasq) fails to send queries out after suspend/resume
reconnects the interface
35 matches
Mail list logo