Comment 3 for bug 330833

I'm confirming this bug. It is a general problem that when network-manager brings up two interfaces and each provides a default route, the latter interface's route clobbers the former's instead of both routes being made available (the classic, sensible behavior).

Upstream fixed bug #288409, which makes it possible to disable configuration of default routes for an interface, but this is not really what you want in the general case - in general, if you have two networks both active and both provide default routes, both of these routes should be made available, not just one or the other. So this is still a bug, even if there's now a way to forcibly disable the default route on a given interface.

This is also related to bug #199140, which is that NM shouldn't be meddling with openvpn connections at all by default.