This appears to be fixed in the current network-manager
(0.7~~svn20080928t225540-0ubuntu1) in intrepid. This issue seems to me
like it comes from network-manager-vpnc's lack of support for importing
the routes (which are handed to nm-vpnc from vpnc) into the network-
manager system. Not sure where to go from there... Should the bug be
marked as Invalid because it pertains to an older release, or Fix
Released since it's in Intrepid and will be officially released soon?

-- 
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

Reply via email to