[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 Is the fix released to Xenial or not? I'm having this problem from years already... And I'm with Xenial still having the problem. -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 Also in artful. bug #1639776 is marked as "fixed" which is fake news. The the other guy above, I often see this after disconnecting from VPN (Cisco AnyConnect). My version: dnsmasq/artful,artful 2.78-1

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

*** 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

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Confirming the bug in Xenial. ** Tags removed: amd64 ** Tags added: xenial ** Description changed: After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working. + + * Also affect Xenial (Unity/GnomeFlashback)since Network-Manager stack + was

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Hi, i've the same problem when i disconnect-reconnect a PPP connection (mobile broadband actually). I 've found a workaround killing dnsmasq in pre-up script of Network-Manager (then, dnsmasq gets automatically restarted). The problem appeared passing from network-manager 1.2.2 to 1.2.6 (while

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

It's fixed in Zesty but not in Yakkety. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working after resume from suspend Status in

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

I see this bug marked as "fix released" in January and that it should be fixed 2.76-4.1, however I only see version 2.76-4 even if I in the "Software & Updates" settings set my "Ubuntu Software" to download from "Main Server". $ apt list dnsmasq Listing... Done dnsmasq/yakkety,yakkety 2.76-4 all

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Same problem Dell XPS 9550 with 16.04.02. Kernel 4.8.0-44 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working after resume from

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

I have also been affected by this bug after upgrading network-manager and related components to 1.2.6-0ubuntu0.16.04.1 from 1.2.2-0ubuntu0.16.04.4 My current workaround is to do: 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

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dnsmasq (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

** Changed in: dnsmasq Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working after resume

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

2.76-4.1 should fix this, uploaded a build to my ppa: https://launchpad.net/~ernstp/+archive/ubuntu/ppa ** Also affects: network-manager via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722 Importance: Unknown Status: Unknown ** Project changed: network-manager => dnsmasq --

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

** Also affects: dnsmasq (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

The Redhat patch is the same patch as the one that fixes Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722 That patch is already upstream, where the debian package seems to be maintained also:

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

The issue reported there seems a bit similar to the one in https://bugzilla.redhat.com/show_bug.cgi?id=1373485 The redhat report has been fixed in dnsmasq with that commit http://pkgs.fedoraproject.org/cgit/rpms/dnsmasq.git/commit/?id=cfdd2cf7648814c9e2c3f938458a2221721dc0c9 ** Bug watch added:

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

** Tags added: nm-improvements -- 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/1631241 Title: Name resolution stops working after resume from suspend Status in

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

I have noticed that doing a "sudo service network-manager restart" usually fixes things, but not always and not for everything. For instance, on my laptop at the moment firefox can't find any webpages ("Server not found"), but Chrome is working fine; ntpd is complaining twice a minute in the log

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

I have the same problem, but only some dns queries stop working. For instance, google.com works fine, while duckduckgo.com doesn't. When trying to ping a server that doesn't work, it fails immediately with the message (translating from Polish, sorry): This name or service is unknown. I have seen

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Hi Martin - not sure if this is related. But this bug report is also indicating problems with dnsmasq when establishing a VPN connection... https://bugs.launchpad.net/ubuntu/+source/openvpn-systemd- resolved/+bug/1636395 Thanks for any help with this. -- You received this bug notification

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Some data points about this: - Name resolution always works fine after first boot - When name resolution is failing, dnsmasq seems to have stop accepting connections on UDP on 120.0.1.1 (TCP seems to work fine) - I can reproduce the issue connecting to wifi at work - WPA2 enterprise wifi

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

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.

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

OK. This could be because NM does not feed it with correct DNS data, or dnsmasq itself gets confused after resuming. Assigning to NetworkManager for now. ** Package changed: systemd (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Status: Incomplete => New --

Re: [Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

On Fri, Oct 7, 2016 at 10:44 PM, Martin Pitt wrote: >> To fix the problem > > Please tell us what actually *is* the problem. My apologies, I should have said "To work around the problem" in the last comment. >> I need to manually edit /etc/resolv.conf and replace

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

> To fix the problem Please tell us what actually *is* the problem. > I need to manually edit /etc/resolv.conf and replace dnsmasq's 127.0.0.1 with resolve's 127.0.0.53 So are you trying to not use NM's dnsmasq instance because that stops working after suspend/resume? -- You received this bug

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Err, I mean "dnsmasq's 127.0.1.1" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working after resume from suspend Status in systemd

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Well I'm posting this from the computer with the problem, so yes I'm online. :) To fix the problem I need to manually edit /etc/resolv.conf and replace dnsmasq's 127.0.0.1 with resolve's 127.0.0.53 (or any other reachable name server). > mjg@payens:~$ nmcli g > STATE CONNECTIVITY WIFI-HW

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Are you sure that you are actually online? What does "nmcli g" say? Does "dig A www.ubuntu.com @8.8.8.8" work? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title:

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

Name resolution, in everything I tried (ping, Epiphany, Geary). Is it normal for dnsmasq to not listen on UDP? > mjg@payens:~$ host vee.net 127.0.1.1 > Using domain server: > Name: 127.0.1.1 > Address: 127.0.1.1#53 > Aliases: > > Host vee.net not found: 5(REFUSED) > mjg@payens:~$ host -T

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

With NetworkManager we switched back to the "dnsmasq" plugin, so it is indeed correct that resolv.conf only contains 127.0.1.1. It also does that without suspending. So what is actually not working? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug