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! ** Attachment added: "Output of NetworkManager and nm-vpnc-service commands" http://launchpadlibrarian.net/15392251/debug-nm.txt -- nm-vpnc and vpnc-connect produce different routing tables https://bugs.launchpad.net/bugs/207506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
