Workaround worked for me and fixed multiple issues! I can use DNS while
being connected to a VPN again :)
Plurtu <email address hidden> schrieb am Sa., 22. Okt. 2016, 10:25:
> More people with the same problem:
> https://ubuntuforums.org/showthread.php?t=2340142
>
> Workaround: Edit /etc/NetworkManager/NetworkManager.conf and remove the
> line "dns=dnsmasq".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633912
>
> Title:
> Problem with DNS resolution after suspend
>
> Status in network-manager package in Ubuntu:
> Confirmed
>
> Bug description:
> I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
> have network issues, one time I was not able to connect to a wifi
> network (might report another bug if this occurees again, but maybe it
> is related, as in network-manager is in some broken state after
> suspend).
>
> Here is whats happening pretty often: After resume from suspend I have
> a solid network connection, no problem to ping machines in LAN or on
> the internet. But DNS resolution is broken until I restart the
> network-manager service.
>
> I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
> should be in there.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: network-manager 1.2.4-0ubuntu1
> ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
> Uname: Linux 4.8.0-22-generic x86_64
> ApportVersion: 2.20.3-0ubuntu8
> Architecture: amd64
> CurrentDesktop: Unity
> Date: Sun Oct 16 21:01:09 2016
> IfupdownConfig:
> # interfaces(5) file used by ifup(8) and ifdown(8)
> auto lo
> iface lo inet loopback
> InstallationDate: Installed on 2016-09-28 (18 days ago)
> InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
> IpRoute:
> default via 192.168.0.1 dev wlp58s0 proto static metric 600
> 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000
> 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
> linkdown
> 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src
> 172.18.0.1
> 192.168.0.0/24 dev wlp58s0 proto kernel scope link src
> 192.168.0.118 metric 600
> NetworkManager.state:
> [main]
> NetworkingEnabled=true
> WirelessEnabled=true
> WWANEnabled=true
> SourcePackage: network-manager
> UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
> nmcli-nm:
> RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING
> WIFI-HW WIFI WWAN-HW WWAN
> running 1.2.4 connected started full enabled
> enabled enabled enabled enabled
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+subscriptions
>
Workaround worked for me and fixed multiple issues! I can use DNS while
being connected to a VPN again :)
Plurtu <email address hidden> schrieb am Sa., 22. Okt. 2016, 10:25:
> More people with the same problem: /ubuntuforums. org/showthread. php?t=2340142 ager/NetworkMan ager.conf and remove the /bugs.launchpad .net/bugs/ 1633912 ature: Ubuntu 4.8.0-22.24-generic 4.8.0 state: ed=true =true /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/1633912/ +subscriptions
> https:/
>
> Workaround: Edit /etc/NetworkMan
> line "dns=dnsmasq".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Problem with DNS resolution after suspend
>
> Status in network-manager package in Ubuntu:
> Confirmed
>
> Bug description:
> I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
> have network issues, one time I was not able to connect to a wifi
> network (might report another bug if this occurees again, but maybe it
> is related, as in network-manager is in some broken state after
> suspend).
>
> Here is whats happening pretty often: After resume from suspend I have
> a solid network connection, no problem to ping machines in LAN or on
> the internet. But DNS resolution is broken until I restart the
> network-manager service.
>
> I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
> should be in there.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: network-manager 1.2.4-0ubuntu1
> ProcVersionSign
> Uname: Linux 4.8.0-22-generic x86_64
> ApportVersion: 2.20.3-0ubuntu8
> Architecture: amd64
> CurrentDesktop: Unity
> Date: Sun Oct 16 21:01:09 2016
> IfupdownConfig:
> # interfaces(5) file used by ifup(8) and ifdown(8)
> auto lo
> iface lo inet loopback
> InstallationDate: Installed on 2016-09-28 (18 days ago)
> InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
> IpRoute:
> default via 192.168.0.1 dev wlp58s0 proto static metric 600
> 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000
> 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
> linkdown
> 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src
> 172.18.0.1
> 192.168.0.0/24 dev wlp58s0 proto kernel scope link src
> 192.168.0.118 metric 600
> NetworkManager.
> [main]
> NetworkingEnabl
> WirelessEnabled
> WWANEnabled=true
> SourcePackage: network-manager
> UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
> nmcli-nm:
> RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING
> WIFI-HW WIFI WWAN-HW WWAN
> running 1.2.4 connected started full enabled
> enabled enabled enabled enabled
>
> To manage notifications about this bug go to:
>
> https:/
>