Ubuntu
network-manager-vpnc package

  1. Bug #207506
  2. Comment #7

Comment 7 for bug 207506

Revision history for this message
Anthony Brock (anthony-brock) wrote :

I am also encountering this issue. Unfortunately, this is also affected several of my customers. I tried to follow the instructions listed at the above link and the results are attached.

As with everyone above, launching vpnc-connect from the command line works perfectly. Here is the routing table before connecting to the VPN:

$ netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.192.126.0 0.0.0.0 255.255.255.128 U 0 0 0 eth0
0.0.0.0 10.192.126.1 0.0.0.0 UG 0 0 0 eth0
$

Here is the routing table after connecting to the VPN:

$ netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
128.193.10.189 10.192.126.1 255.255.255.255 UGH 0 0 0 eth0
10.192.126.0 0.0.0.0 255.255.255.128 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 tun0
$

Any ideas if a fix is in the works? My customers have discovered that the official Linux VPN from Cisco has stopped functioning and are trying to shift to vpnc. However, the default "full tunnel" configuration is causing some issues. Thanks!