n-m-openvpn: default route is erased even if none is pushed by server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-openvpn (Debian) |
New
|
Unknown
|
|||
network-manager-openvpn (Fedora) |
Invalid
|
Unknown
|
|||
network-manager-openvpn (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-
Description: Ubuntu intrepid (development branch)
Release: 8.10
Source package : network-
Version : 0.7~~svn2008092
Before making the connection my routing-table looks like this :
10.0.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 10.0.2.2 0.0.0.0 UG 0 0 0 eth0
after connecting to my openvpn server it looks like this ( i don't push routes to my vpn clients) :
The X's represent my openvpn server
xxx.xxx.xxx.xxx 10.0.2.2 255.255.255.255 UGH 0 0 0 eth0
10.11.12.0 0.0.0.0 255.255.255.0 U 0 0 0 tap0
10.0.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 tap0
what i'm expecting is a routing table like this :
10.0.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 10.0.2.2 0.0.0.0 UG 0 0 0 eth0
10.11.12.0 0.0.0.0 255.255.255.0 U 0 0 0 tap0
there's no need for the network-manager to alter my default gw since i don't want my traffic to be routed through the vpn connection
Changed in network-manager-openvpn: | |
status: | Unknown → New |
Changed in network-manager-openvpn: | |
status: | Unknown → Confirmed |
Changed in network-manager-openvpn (Fedora): | |
status: | Confirmed → Invalid |
This bug also affects hardy. Every push route entry in the openvpn server.conf is ignored by the network- manager- openvpn module in tap mode. It always sets the route 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 tap0. Therefore the module isn't usable at the moment.