MaGoo, please open a separate bug for your issue, as it is related to
the openvpn plugin and not the VPNC plugin.
It appears to me like this bug has really been fixed since Intrepid or
Jaunty, following the initial description from the bug reporter: routes
now being imported by the plugin from vpnc, they are now "the same",
depending on whether or not split-tunnelling is expected in your
environment, which is another issue entirely.
I'm closing this bug since the initial issue has been resolved a long
time ago. If you feel the default setting for "Use this connection only
for resources on its network" should be changed, please open a separate
bug on the issue (which should also be filed upstream and discussed on
the NM mailing list).
** Changed in: network-manager-vpnc (Ubuntu)
Status: Confirmed => Fix Released
--
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
