n-m-openvpn: default route is erased even if none is pushed by server

[Robert Buhren]

Binary package hint: network-manager-openvpn

Description: Ubuntu intrepid (development branch)
Release: 8.10

Source package : network-manager-openvpn
Version : 0.7~~svn20080928t225540-0ubuntu1

Before making the connection my routing-table looks like this :

10.0.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 10.0.2.2 0.0.0.0 UG 0 0 0 eth0

after connecting to my openvpn server it looks like this ( i don't push routes to my vpn clients) :
The X's represent my openvpn server

xxx.xxx.xxx.xxx 10.0.2.2 255.255.255.255 UGH 0 0 0 eth0
10.11.12.0 0.0.0.0 255.255.255.0 U 0 0 0 tap0
10.0.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 tap0

what i'm expecting is a routing table like this :

10.0.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 10.0.2.2 0.0.0.0 UG 0 0 0 eth0
10.11.12.0 0.0.0.0 255.255.255.0 U 0 0 0 tap0

there's no need for the network-manager to alter my default gw since i don't want my traffic to be routed through the vpn connection

[Bjoern Ricks (bjoern-ricks-googlemail)]

This bug also affects hardy. Every push route entry in the openvpn server.conf is ignored by the network-manager-openvpn module in tap mode. It always sets the route 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 tap0. Therefore the module isn't usable at the moment.

[Joseph (joenmtl)]

In a recent change to network-manager-openvpn that came after Hardy Beta release, I had trouble accessing machines on the other side of the vpn. After troubleshooting the problem, I found that the routing of subnet 10.0.0.0 is going not to the vpn device. This was working fine between Alpha 4 and Beta.

10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 tap0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

I have to manually edit the routing table to get it to work.

[Aldrin Martoq (amartoq)]

This bug affects me too, after upgrading from 8.04 -> 8.10 I had to recreate the VPN connections.

I use TAP device, and networkmanager replaces the default route using gw 0.0.0.0 in device tap which is wrong. I tried changing some settings in the advanced tabs but no luck. Installed version is:
network-manager-openvpn 0.7~~svn20081015t024626-0ubuntu1

Thanks,

[hads (hads)]

I've just run across this issue also. Using Intrepid

[Lionel Porcheron (lionel.porcheron)]

This issue is still present in jaunty.

As a workaround, you can go in the VPN configuration screen in Network Manager, IPv4 Settings tab, routes and check last option "Use this connexion only for resources on its network".

[Lionel Porcheron (lionel.porcheron)]

This problem even if reported on -openvpn plugin does not look specific to -openvpn.

[Thierry Carrez (ttx)]

Looks like a duplicate of bug 330833... There is a workaround described there.