#584578 network-manager-vpnc: incorrectly adds a route through the current network gateway

Package:
network-manager-vpnc
Source:
network-manager-vpnc
Description:
network management framework (VPNC plugin core)
Submitter:
Teodor
Date:
2010-06-04 18:45:05 UTC
Severity:
normal
#584578#5
Date:
2010-06-04 18:43:48 UTC
From:
To:
Hi,

I've added for now two Cisco VPN connections and I've noticed that it adds a route
to the VPN server through the current network gateway like this:
| root@frost:~# ip route list
| [..]
| t.x.y.18 via CURRENT_GW dev eth0  proto static	[1]
| t.x.y.18 via ANOTHER_VPN dev tun0			[2]
| [..]
| default via CURRENT_GW dev eth0  proto static

The problem is that the Cisco VPN server is only reachable through another VPN
connection which was established first and listed as the second route above:
| t.x.y.18 via ANOTHER_VPN dev tun0

But this route is ignored because it was overriden by the first route added by
network-manager-vpnc at connection time even if the Cisco VPN connection was
configured with "Use this connection only on resources on this network" (does
not became the default route). The direct result of this route is that the VPN
connection is not working at all unless the route [1] is manually deleted.

The fix is to not add a new route to the VPN server through CURRENT_GW unless
the new Cisco VPN connection will become the default route.

Thanks