Was facing the same "issues" ... But now, reading all the comments, I'm starting to think it is no issue at all : it's not a bug, it's a feature :-)
Put simply :
- Either you need specific routes through your VPN, then it means you obviously want to keep your client's default route through its local interface,
- Or, you need your client's default route to be via the VPN, then there is no need to specifically set the other routes via the VPN ... as the VPN is the default route...
So finally I am very happy with the way the network-manager works for the moment : I need to decide where my default route would go through, and only configure alternate routes.
If these are not through the VPN, I configure them in the local interface. If they are through the VPN, I configure them in the VPN interface and the VPN client adds the routes pushed from the server.
Now, I have to admit the the "Ignore automatically obtained routes" is really really really misleading !!!!
Hope this helps.
Hello all,
Was facing the same "issues" ... But now, reading all the comments, I'm starting to think it is no issue at all : it's not a bug, it's a feature :-)
Put simply :
- Either you need specific routes through your VPN, then it means you obviously want to keep your client's default route through its local interface,
- Or, you need your client's default route to be via the VPN, then there is no need to specifically set the other routes via the VPN ... as the VPN is the default route...
So finally I am very happy with the way the network-manager works for the moment : I need to decide where my default route would go through, and only configure alternate routes.
If these are not through the VPN, I configure them in the local interface. If they are through the VPN, I configure them in the VPN interface and the VPN client adds the routes pushed from the server.
Now, I have to admit the the "Ignore automatically obtained routes" is really really really misleading !!!!
Hope this helps.