Comment 26 for bug 330833

I've been affected by this bug for since Hardy and surprised to still see it in Lucid. Checking "Use this connection only for resources on its network" is unacceptable for those who need to use the VPN as a way of securing traffic on public hotspots. I normally run an autovpn script that I found online that brings up the VPN after a connection change, like when a wifi interface is brought up, and in that script I'll fix my default gateway.

But today, I noticed that while on a local wifi router that had a different subnet than the one my openvpn server is on, the routes were set fine and I had no issues. Heres the scenario that works using stock nm-openvpn:
 Local wifi router on 192.168.1.0/24 --> Internet
 Remote Openvpn router/server 192.168.0.1/24 --> Internet

The scenerio that doesn't work using nm-openvpn unless default route is modified after vpn up:
 Local wifi router on 192.168.0.0/24 --> Internet
 Remote Openvpn router/server 192.168.0.1/24 --> Internet

Of course, the VPN subnet is on a different subnet than the local ones, 10.0.0.0/24, but thats not a factor.

Perhaps this will help someone?