Eddie split routes for management traffic on AWS

[vpn-support 0]

Hi,

 

I wanted to make the default route through the tun0 interface to route all traffic through vpn. However, I want to keep the existing route (or access) on my aws instance in order to still ssh/rdp into the vm outside the VPN traffic by using the public ip assigned by AWS. Right now with defaults, not removing the gateway after the vpn connects forwards no traffic and removing the default gw kills the ssh/rdp connection.

 

Whats the best way here using Eddie? I figured route is not enough since making a simple route add back to the previous default gw still breaks ssh after the vpn associates, like

route add -net 172.31.0.0 netmask 255.255.255.0 gw 172.31.0.1 eth0, but that seems wrong.

 

How can I do this?