This problem presented itself to me during the upgrade from Intrepid to Jaunty, with no other changes to the network or VPN setup. On Intrepid, everything worked fine. On Jaunty (beta as of 4/18/2009), all traffic was going to the VPN which was not properly resolving Internet domains (e.g., yahoo.com).
Applying Doug's fix (https://bugs.launchpad.net/ubuntu/+source/network- manager-vpnc/+bug/207506/comments/13) by checking "Use this connection for resources on its network" fixed the problem. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
