Public bug reported:

When using a connection defined in the NetworkManager applet and
initiated from the applet, an openvpn connection does not respect the
routes pushed to the client by the server. When I make the connection
from the applet, my routing tables (route -n) looks like this (which is
incorrect):

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.25.1    0.0.0.0         UG    100    0        0 
enp0s31f6
10.190.192.0    192.168.25.30   255.255.255.0   UG    100    0        0 
enp0s31f6
10.219.27.0     0.0.0.0         255.255.255.0   U     50     0        0 tun0
52.24.197.4     192.168.25.1    255.255.255.255 UGH   100    0        0 
enp0s31f6
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 
enp0s31f6
192.168.25.0    0.0.0.0         255.255.255.0   U     100    0        0 
enp0s31f6
192.168.25.1    0.0.0.0         255.255.255.255 UH    100    0        0 
enp0s31f6

If I export the configuration for that connection to a file called
"myvpn.ovpn", and then run `sudo openvpn myvpn.ovpn`, my routing table
looks like this (which is what I think it should be):

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.25.1    0.0.0.0         UG    100    0        0 
enp0s31f6
10.190.192.0    192.168.25.30   255.255.255.0   UG    100    0        0 
enp0s31f6
10.219.27.0     0.0.0.0         255.255.255.0   U     0      0        0 tun0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 
enp0s31f6
172.30.0.0      10.219.26.1     255.255.0.0     UG    0      0        0 tun0
192.168.25.0    0.0.0.0         255.255.255.0   U     100    0        0 
enp0s31f6

The 172.30/16 route over the tun0 interface does not happen if I make
the connection from the applet.

The behavior seems to be new in Zesty, as I recently did a clean install
and set this up.

The same configuration worked correctly as far as I can tell in Xenial
and Yakkety.

ALSO NEED INFO:

1. Ubuntu Release: Ubuntu 17.04 amd64
2. Version of network-manager-openvpn: 1.2.6-2ubuntu1
3. Expected to happen: Routing table when connecting to VPN from applet should 
match routing table when connecting to openvpn from the command line using the 
configuration exported from the applet.
4. Actually happened: Routing table when connecting from applet does not get 
route pushed by the server. Routing table when connecting using the command 
line and the configuration exported by the applet DOES get route pushed by the 
server.

ADDITIONAL:

The box for "Use this connection only for resources on its network" is
checked in the IPv4 Settings for this connection.

I've attached the myvpn.ovpn file that I exported from the applet.

Please let me know if I can provide any additional information.

** Affects: network-manager-openvpn (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "The exported openvpn config file (remote name changed to 
example.com)"
   https://bugs.launchpad.net/bugs/1697554/+attachment/4894865/+files/myvpn.ovpn

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1697554

Title:
  Openvpn connection not respecting routes pushed by server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1697554/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to