NetworkManager add unnecessary route entry for VPN connection

I'd like to confirm I have the same bug using 64bit Intrepid with all updates as of 11th December 2008.

I can resolve the issue by placing a script in /etc/ppp/ip-up.d/ that removes the erroneous route with "route del foo"

The bug seems to be rather global in NetworkManager. It also happens in n-m-openvpn:

VPN disconnected:
celestia:~# ip ro
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.137 metric 2
default via 192.168.1.1 dev wlan0 proto static

VPN connected:
celestia:~# ip ro
x.x.x.x via 192.168.1.1 dev wlan0 proto static
x.x.x.x via 192.168.1.1 dev tun0 proto static
192.168.1.1 dev tun0 proto static scope link
10.0.1.1 dev tun0 proto kernel scope link src x.x.x.x
x.x.x.x/x via 10.0.1.1 dev tun0 proto static
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.137 metric 2
default via 192.168.1.1 dev wlan0 proto static

The third line must not be there, otherwise I can connect neither to VPN hosts nor to other hosts
in the net.

The hack-solution is to add these:
    vpn-up)
        /bin/ip ro del 192.168.1.1 dev tun0
        ;;

to /etc/NetworkManager/dispatcher.d/01ifupdown but the proper solution is not to add
broken routes in the first place.

Sorry, forgot to post the versions

celestia:~# dpkg -l *network-manager* | grep ii
ii network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 network management framework daemon
ii network-manager-gnome 0.7.1~rc4.1-0ubuntu2 network management framework (GNOME frontend
ii network-manager-openvpn 0.7.1~rc4.1.20090323+bzr27-0ubuntu2 network management framework (OpenVPN plugin

Same bug here (nm 0.7.1~rc4).

Paulus's edit to 01ifupdown works great. (Thanks!)

I'd love to see a "Set default route" option as part of the config, defaulting to off for consistency with the openvpn command line client.

Status changed to 'Confirmed' because the bug affects multiple users.