networkmanager sets wrong default route

[Christian González]

Binary package hint: network-manager

i just upgraded from intrepid to jaunty,
In intrepid everything worked fine with VPN, now jaunty sets the wrong default route.

my resolv.conf just has 1 line per default, using my wired dhcp connection:

nameserver 192.168.9.1

when I start the vpn connenction, it looks like this:

# Generated by NetworkManager
domain blah.blah.at
search blah.blah.at
nameserver 10.10.210.254
nameserver 192.168.9.1

route without VPN (works)
192.168.9.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 192.168.9.1 0.0.0.0 UG 0 0 0 eth0

route with VPN started:
x.x.x.x (remote gw) 192.168.9.1 255.255.255.255 UGH 0 0 0 eth0
10.10.100.0 0.0.0.0 255.255.255.0 U 0 0 0 tap0
10.10.210.0 10.10.100.1 255.255.255.0 UG 0 0 0 tap0
192.168.9.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 10.10.100.1 0.0.0.0 UG 0 0 0 tap0

so the last line here is set, and all traffic would go over the tap device - which is of course blocked by the remote server.
The VPN server pushes the route 10.10.210.0, that one is added correctly.

But it is NOT good that NM sets up the default route over the vpn device!
This renders VPN unusable!