(Cisco) VPN name resolution breaks after upgrade to 1.2.2-0ubuntu0.16.04.3

Bug #1633003 reported by Jeroen Ruigrok van der Werven
24
This bug affects 5 people
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/apt/history.log I noticed these were the updates:

Start-Date: 2016-10-13 09:00:37
Commandline: apt dist-upgrade
Requested-By: jeroenr (1000)
Upgrade: libnm-glib4:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libsystemd0:amd64 (229-4ubuntu10, 229-4ubuntu11), libsystemd0:i386 (229-4ubuntu10, 229-4ubuntu11), libdbusmenu-glib4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), google-chrome-stable:amd64 (53.0.2785.143-1, 54.0.2840.59-1), libnm-glib-vpn1:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), udev:amd64 (229-4ubuntu10, 229-4ubuntu11), libnm0:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), network-manager:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libdbusmenu-gtk4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), kbd:amd64 (1.15.5-1ubuntu4, 1.15.5-1ubuntu5), libudev1:amd64 (229-4ubuntu10, 229-4ubuntu11), libudev1:i386 (229-4ubuntu10, 229-4ubuntu11), libnm-util2:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libappstream-glib8:amd64 (0.5.13-1ubuntu3, 0.5.13-1ubuntu4), gnome-calculator:amd64 (1:3.18.3-0ubuntu1, 1:3.18.3-0ubuntu1.16.04.1), systemd-sysv:amd64 (229-4ubuntu10, 229-4ubuntu11), libpam-systemd:amd64 (229-4ubuntu10, 229-4ubuntu11), systemd:amd64 (229-4ubuntu10, 229-4ubuntu11), gir1.2-dbusmenu-glib-0.4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), libdbusmenu-gtk3-4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), lightdm:amd64 (1.18.2-0ubuntu2, 1.18.3-0ubuntu1), liblightdm-gobject-1-0:amd64 (1.18.2-0ubuntu2, 1.18.3-0ubuntu1)
End-Date: 2016-10-13 09:01:06

After downloading version 1.2.2-0ubuntu0.16.04.1 copies of libnm-glib-vpn1:amd64 libnm-glib4:amd64 libnm-util2:amd64 libnm0:amd64 network-manager:amd64 and installing them via: sudo -H dpkg -i *.deb my name resolution started working again.

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.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
     1.2.2-0ubuntu0.16.04.3 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
        100 /var/lib/dpkg/status
     1.1.93-0ubuntu4 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
libnm-glib4:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
     1.2.2-0ubuntu0.16.04.3 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
        100 /var/lib/dpkg/status
     1.1.93-0ubuntu4 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
libnm-util2:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
     1.2.2-0ubuntu0.16.04.3 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
        100 /var/lib/dpkg/status
     1.1.93-0ubuntu4 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
libnm0:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
     1.2.2-0ubuntu0.16.04.3 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
        100 /var/lib/dpkg/status
     1.1.93-0ubuntu4 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
network-manager:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
     1.2.2-0ubuntu0.16.04.3 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
        100 /var/lib/dpkg/status
     1.1.93-0ubuntu4 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
% apt-cache policy vpnc
vpnc:
  Installed: 0.5.3r550-2build1
  Candidate: 0.5.3r550-2build1
  Version table:
 *** 0.5.3r550-2build1 500
        500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status

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>

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

This issue is not just Cisco vpnc specific; it also happens with openVPN and possibly all VPN connections.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.