I am also affected by this bug. While I agree with Johan that allowing the client a direct route to the internet while the tunnel is active is a Bad Thing, that is ultimately the decision of the network architect, not the client. I believe that the client should route whatever networks are advertised by the VPN gateway; if that includes the default route, then so be it.
The reality of the situation is that network administrators are often configuring their VPNs based on the behaviour of the Windows client, and aren't necessarily about to make changes for one or two Linux users in the enterprise. While the NetworkManager vpnc plugin does allow you to manually enter which networks are to be routed through the tunnel, doing so prevents NM from correctly updating resolv.conf to use the organization's DNS servers, which breaks name resolution for hosts on the private network. -- No default internet traffic after connecting to VPN https://bugs.launchpad.net/bugs/124663 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
