(Cisco) VPN name resolution breaks after upgrade to 1.2.2-0ubuntu0.16.04.3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After upgrading my 16.04 installation today I noticed my VPN sessions suddenly had no name resolution anymore.
Digging through /var/log/
Start-Date: 2016-10-13 09:00:37
Commandline: apt dist-upgrade
Requested-By: jeroenr (1000)
Upgrade: libnm-glib4:amd64 (1.2.2-
End-Date: 2016-10-13 09:01:06
After downloading version 1.2.2-0ubuntu0.
Additional information:
% lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
% apt-cache policy libnm-glib-vpn1 libnm-glib4 libnm-util2 libnm0 network-manager
libnm-glib-vpn1:
Installed: 1.2.2-0ubuntu0.
Candidate: 1.2.2-0ubuntu0.
Version table:
1.
500 http://
*** 1.2.2-0ubuntu0.
100 /var/lib/
1.
500 http://
libnm-glib4:
Installed: 1.2.2-0ubuntu0.
Candidate: 1.2.2-0ubuntu0.
Version table:
1.
500 http://
*** 1.2.2-0ubuntu0.
100 /var/lib/
1.
500 http://
libnm-util2:
Installed: 1.2.2-0ubuntu0.
Candidate: 1.2.2-0ubuntu0.
Version table:
1.
500 http://
*** 1.2.2-0ubuntu0.
100 /var/lib/
1.
500 http://
libnm0:
Installed: 1.2.2-0ubuntu0.
Candidate: 1.2.2-0ubuntu0.
Version table:
1.
500 http://
*** 1.2.2-0ubuntu0.
100 /var/lib/
1.
500 http://
network-manager:
Installed: 1.2.2-0ubuntu0.
Candidate: 1.2.2-0ubuntu0.
Version table:
1.
500 http://
*** 1.2.2-0ubuntu0.
100 /var/lib/
1.
500 http://
% apt-cache policy vpnc
vpnc:
Installed: 0.5.3r550-2build1
Candidate: 0.5.3r550-2build1
Version table:
*** 0.5.3r550-2build1 500
500 http://
100 /var/lib/
Expected
After updating that connecting to my existing and working Cisco VPN would work
What happened
Name resolution failed. Could not ping hosts over VPN anymore.
Most likely cause
It seems that /etc/resolv.conf is not getting the search argument added to the file anymore. With .3 installed I only had a nameserver 127.0.0.1 line. Now with .1 installed I see that I have both that nameserver 127.0.0.1 line as well as search <VPN DNS domain>
Status changed to 'Confirmed' because the bug affects multiple users.