The issue is fixed in Ubuntu 17.10, it's not likely to get SRUed to the
previous stable now though
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1691996
Title:
DNS and search domain is not pushed to systemd-resolved sometimes
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
I have an OpenVPN connection with statically configured DNS server
address and the search domain. When this connection is established,
there is a high chance that the DNS address and the search domain are
not pushed to systemd-resolved for this connection. The problem does
not reproduce reliably, sometimes the parameters are pushed. When the
parameters are not pushed, 'systemd-resolve --status' reports no DNS
servers or DNS domain for the VPN connection, and name resolution does
not work.
This bug has been reportedly fixed upstream in NetworkManager 1.8. The
upstream bug reports are:
https://bugzilla.gnome.org/show_bug.cgi?id=782597
https://bugzilla.gnome.org/show_bug.cgi?id=779087
Please, update NetworkManager shipped with Ubuntu or backport the fix.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
Uname: Linux 4.10.0-16.1-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Fri May 19 13:35:42 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-05-01 (748 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
default via 192.168.1.1 dev eth0 proto static metric 100
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2017-05-11T15:26:12.449289
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
virbr0 bridge connected /org/freedesktop/NetworkManager/Devices/2
virbr0 a80bff56-e5d6-4fa4-b544-89cb3c389e3b
/org/freedesktop/NetworkManager/ActiveConnection/0
eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/1
Wired connection 1 44a70bab-e44e-3942-8259-e96eb6f3fe5b
/org/freedesktop/NetworkManager/ActiveConnection/2
lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0
-- -- --
virbr0-nic tun unmanaged /org/freedesktop/NetworkManager/Devices/3
-- -- --
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.4.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/1691996/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
