[Bug 364844] Re: network-manager-vpnc produces incorrect routing table

[Mathieu Trudel-Lapierre]

JRavasi, I'm not convinced this patch really is applicable to all cases;
I'm concerned it might break other things for different cases where the
netmask is not provided (e.g. what if just 0.0.0.0 is given as an
address?). In general, it sounds as though a missing netmask is really
an issue with the vpn endpoint used, but I'm just going from memory
there. In any case, it would be beneficial if you could provide details
(logs and all) as to why this is required. This should be done in a
separate bug report.

Also please, send this patch to the NetworkManager mailing list for
review: http://mail.gnome.org/mailman/listinfo/networkmanager-list

As far as I know, the initial issue has been resolved in Karmic or at
worst in Lucid with the use of the "Use this connection only for the
resources on its network" checkbox. If you find that it has not; please
file a new bug using 'ubuntu-bug' and providing the exact routes you are
getting along with the ones you are expecting so we can fix it.

I'll mark this Fix Released because there has been reports of this bug
being fixed with the checkbox that was introduced in (Karmic or Lucid);
this doesn't mean everything is fixed, but does mean that we'll need
new, separate reports to figure out what else may be wrong.

** Changed in: network-manager-vpnc (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Review Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/364844

Title:
  network-manager-vpnc produces incorrect routing table

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/364844/+subscriptions