Magnus, I'll submit a new bug, once I can confirm that it's not OpenVPN specific. At least I suspect that the DHCP lease renewal will nuke the link-local 169.254.0.0/16 route regardless of OpenVPN being in use or not. OpenVPN is just hit harder due to the fact that the host route is absolutely necessary for VPN to work if the VPN-gateway resides within one of the networks routed inside the tunnel, but it would probably just be an incarnation of the same bug which is basically bad handling of DHCP renewals. However I'll have to wait some hours for the DHCP lease to expire first. :-)
Alexander, there was some activity in the GNOME bug tracker, and a setting called «Ignore automatically obtained routes» was mentioned. It defaults to off, which is what I would want it to be (or so I thought), but out of curiousity, I tried to enable that setting, and surprisingly enough - now it works! So the logic is incorrectly reversed in the NM-openvpn code that handles that setting - if you ask it to ignore the VPN server routes, NM-openvpn will respect them, and vice verca. The NM developer commenting there said that « [y]ou also must have at least NM svn r4181 or later as well as NetworkManager-openvpn r4170 or later», so maybe the bug is already fixed upstream. (I'm not sure though, his comment was to me a bit unclear in some places). Michael & JB: Can you confirm that enabling «Ignore automatically obtained routes» (you'll find it in IPv4 Settings -> Routes... in the config editor) causes the default route to be installed as expected? Tore -- Intrepid regression: default route is no longer redirected over VPN tunnel https://bugs.launchpad.net/bugs/269071 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
