I'd have to respectfully disagree -- although I ran into the same problem and also find it annoying to have to go so far to fix such a simple issue -- AFAIK, checking this effectively enables what is called "Split-tunnelling", and is considered a potential security issue in many environments.
On the other hand, it is true that in many cases the tunnels are specified in a list, and 0.0.0.0 usually isn't part of it (because otherwise, why use a list?). Personally, I'd bring the issue upstream on the NetworkManager mailing list, or create a specific bug, since it seems to me like it's a different issue. -- 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
