Network Manager does not set up routed OpenVPN connection correctly

Binary package hint: network-manager

Some of the components of this bug are simlar to other posted bugs, but I have not seen a bug report that specifically deals with with routed OpenVPN networks. Connecting to a routed OpenVPN network using only the OpenVPN service works correctly. The server being connected to does not push any DNS information and only pushes one route to provide access to servers on its class C IP network. The connection uses X.509 certificates.

Original contents of /etc/resolv.conf:

    # generated by NetworkManager, do not edit!
    search mydomain.pvt
    nameserver 192.168.75.200

Original routing table before VPN connection:

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.75.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
    0.0.0.0 192.168.75.1 0.0.0.0 UG 0 0 0 eth0

Expected results (these results are achieved after sudo /etc/init.d/openvpn start):

    /etc/resolv.conf unchanged

Routing table has the one pushed route from the VPN server plus the VPN route:

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    10.8.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
    192.168.99.0 10.8.0.1 255.255.255.0 UG 0 0 0 tun0
    192.168.75.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
    0.0.0.0 192.168.75.1 0.0.0.0 UG 0 0 0 eth0

Actual results when using the network manager to make the VPN connection:

/etc/resolv.conf is empty

Routing table is wrecked:

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    xxx.xxx.xxx.xxx 192.168.75.1 255.255.255.255 UGH 0 0 0 eth0
    192.168.99.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0
    192.168.75.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
    0.0.0.0 192.168.75.1 0.0.0.0 UG 0 0 0 eth0

xxx.xxx.xxx.xxx (actual IP obscured only in this bug report) is the internet IP of the VPN gateway, which is showing up in the routing table, but the VPN route for 10.8.0.1 is not added and the route for 192.168.99.0/24 is changed and unusable as well.

Since a good connection can be made to the server using just the /etc/init.d/openvpn service, but the same machine cannot make a valid connection with the network manager using the same certificates, the problem appears to be in the network manager.

This is using Ubuntu 7.10 with all updates as of 2008-Apr-18.

Packages:

openvpn:
  Installed: 2.0.9-8
  Candidate: 2.0.9-8
  Version table:
 *** 2.0.9-8 0
        500 http://archive.ubuntu.com gutsy/universe Packages
        100 /var/lib/dpkg/status

network-manager:
  Installed: 0.6.5-0ubuntu16
  Candidate: 0.6.5-0ubuntu16
  Version table:
 *** 0.6.5-0ubuntu16 0
        500 http://archive.ubuntu.com gutsy/main Packages
        100 /var/lib/dpkg/status

network-manager-gnome:
  Installed: 0.6.5-0ubuntu10
  Candidate: 0.6.5-0ubuntu10
  Version table:
 *** 0.6.5-0ubuntu10 0
        500 http://archive.ubuntu.com gutsy/main Packages
        100 /var/lib/dpkg/status