Network Manager fails to require VPN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
In Network Manager you can require that the local network requires a particular VPN connection. This works without issue, when networking is enabled, VPN connects automatically. But should there be any service interruption, Network Manager will reconnect using the local network and then exposing the real IP address.
This issue only started to occur in 18.04 using GNome desktop environment. This was not an issue in 16.04 using GNome or Unity.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 1 16:16:08 2018
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2018-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
default via 192.168.7.1 dev enp0s3 proto dhcp metric 100
169.254.0.0/16 dev enp0s3 scope link metric 1000
192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 100
IwConfig:
enp0s3 no wireless extensions.
lo no wireless extensions.
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-
Wired connection 1 f6168b50-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
enp0s3 ethernet connected /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.10.6 connected started full enabled enabled enabled enabled enabled
Please reproduce the problem, do a hard reset and then run this command:
journalctl -b-1 > prev_boot.txt
and send us the resulting file prev_boot.txt