@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 added and
removed from the system."
I see no details or data in this bug, nor the RH bugzilla that indicates that
resolvconf itself has an issue. If you have
more information on this, then please do add that;
Specifically to the recent upgrade to resolvconf (I included the diff of
change); there is no runtime code change; only a systemd unit change on
when the service is started. Even if there is some bug in resolvconf as
you say; it will occur in the previous version and the updated version
since the update did not modify any of the resolvconf runtime code.
If you believe that the *unit* change to resolvconf in 1.78ubuntu4 is
related to this issue, please add that specific information before
reopening the resolvconf task.
Finally, it does appear that there should be a dnsmasq task; I'll
nominate that.
** Changed in: resolvconf (Ubuntu)
Status: Confirmed => Invalid
--
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 being used after network-manager
upgrade to 1.2.6-0ubuntu0.16.04.1
Status in network-manager package in Ubuntu:
Confirmed
Status in resolvconf package in Ubuntu:
Invalid
Bug description:
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 1.2.2-0ubuntu0.16.04.4 solves the problem.
Steps for reproducing:
1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to
version 1.2.6-0ubuntu0.16.04.1
2. connect to VPN via network-manager applet
3. nslookop servername.internal --> ** server can't find servername.internal:
NXDOMAIN
4. disconnect from VPN via network-manager applet
5. roll back network-manager via command: sudo apt-get install
network-manager=1.2.2-0ubuntu0.16.04.4
6. restart network-manager via sudo service network-manager restart
7. connect to VPN via network-manager applet
8. nslookop servername.internal --> the server is resolved correctly
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 9 19:49:55 2017
InstallationDate: Installed on 2015-10-05 (520 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.2.6 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/1671606/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
