Comment 15 for bug 194487
Revision history for this message
| Diego Rivera (diego-rivera-rbxglobal) wrote | #15 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Yes, this is still an issue. I can confirm what our friend said earlier about routes being correctly added by OpenVPN and subsequently being removed (presumably by NetworkManager or the NM-OpenVPN plugin).
In my view the problem is that the options do not permit the selection of the correct behavior. There are 3 possible scenarios:
1) User explicitly chooses to use the server as the default gateway ("user-
2) User does NOT explicitly choose to use the server as the default gateway, and wants to specify which targets to route manually over the tunnel (current behavior)
3) Same as case 2, but add to that the acceptance of server-provided routing info (this is the case not functioning). In this case, manual routes may also make sense as manual, forced exclusions or routes augmenting the routes received from the server (i.e. 10.0.0.0/8, !10.5.0.0/24).
I'm willing to work on fixing this, but I need insights as to where in NM or NM-OpenVPN the routes are removed so I can add the logic to selectively do that only when appropriate.
Anyone care to help me get started?