[Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Mariano Draghi]

I've manually applied the patch proposed in comment #22 to my Ubuntu
18.10 desktop, and I can confirm that it fixes the issue for me. I
haven't seen any regression either, although my testing has been very
limited so far.

I've been experiencing this bug ever since Ubuntu 18.04 when
disconnecting from my employer's Fortinet SSLVPN (I'm using the network-
manager-fortisslvpn package). My previous workaround was to force my
wifi up again (even if it was not down) after closing the VPN connection
(nmcli c up $my-ssid).

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1778946

Title:
  No dns resolution after closing a vpn/pptp connection

Status in ppp package in Ubuntu:
  Confirmed
Status in ppp package in Debian:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lo        no wireless extensions.
   
   eth0      no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE      STATE      DBUS-PATH                                  CONNECTION           CON-UUID                              CON-PATH                                           
   eth0    ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  Connexion filaire 1  94806bba-1c68-46b6-87f4-a3eeeeaff6dd  /org/freedesktop/NetworkManager/ActiveConnection/6 
   lo      loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --                   --                                    --
  nmcli-nm:
   RUNNING  VERSION  STATE                  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI     WWAN-HW  WWAN    
   running  1.10.6   connected (site only)  started  limited       enabled     enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1778946/+subscriptions