Jump to content
Not connected, Your IP:
Sign in to follow this  

Eddie split routes for management traffic on AWS

Recommended Posts



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 netmask gw eth0, but that seems wrong.


How can I do this?

Share this post

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  

  • Create New...