NetworkManager always overwrites default route when connecting to OpenVPN network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager-OpenVPN |
Invalid
|
High
|
|||
network-manager (Debian) |
New
|
Unknown
|
|||
network-manager (Fedora) |
Invalid
|
Medium
|
|||
network-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
network-manager-openvpn (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: network-manager
My office VPN has IMAP, (forwarding) DNS services and not much else. It doesn't forward client traffic to the Internet. This means I can't use the VPN server as a default gateway.
Every time I connect to the VPN using NetworkManager/
As it is right now, I have to connect to the VPN, delete the default route, and re-add my wireless router as the default gateway before I can have both email and web access.
See attached routing table details.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
NonfreeKernelMo
Package: network-manager 0.7-0ubuntu1~
ProcEnviron:
PATH=/
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
Uname: Linux 2.6.27-11-generic i686
affects: | network-manager (Ubuntu) → network-manager-openvpn (Ubuntu) |
tags: |
added: jaunty regression-release removed: regression-potential |
Changed in network-manager (Fedora): | |
status: | Unknown → Confirmed |
Changed in network-manager (Debian): | |
status: | Unknown → New |
Changed in network-manager-openvpn: | |
status: | Unknown → New |
Changed in network-manager (Fedora): | |
status: | Confirmed → Invalid |
Changed in network-manager-openvpn: | |
status: | New → Invalid |
Changed in network-manager-openvpn: | |
importance: | Unknown → High |
Changed in network-manager (Fedora): | |
importance: | Unknown → Medium |
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.