Skip to content
Connecting to two different OpenVPN servers at the same time
Got a problem with Viscosity or need help? Ask here!
Hello,
I am not a guru on networking neither VPNs but I am facing the following issue:
I have TWO VPNs. Each one allows me to ssh a series of servers and connect to a DB server. I want to be connected to both so I can easily do my work.
Server 1:
ssh: 192.170.20.*
DB: server1.rds.amazonaws.com
Server 2:
ssh: 192.120.15.*
DB: server2.rds.amazonaws.com
When I connect, I can reach only the server for the first connection made, so I know everything is going there, even when I set each VPN connection like:
Connection 1:
DNS Settings: Split DNS
Servers: 192.170.20.0/1, server1.rds.amazonaws.com
and
Connection 2:
DNS Settings: Split DNS
Servers: 192.120.15.0/1, server2.rds.amazonaws.com
Please don't laugh too much about my question.... and your time and help is greatly appreciated.
Regards,
Juan Luna
I am not a guru on networking neither VPNs but I am facing the following issue:
I have TWO VPNs. Each one allows me to ssh a series of servers and connect to a DB server. I want to be connected to both so I can easily do my work.
Server 1:
ssh: 192.170.20.*
DB: server1.rds.amazonaws.com
Server 2:
ssh: 192.120.15.*
DB: server2.rds.amazonaws.com
When I connect, I can reach only the server for the first connection made, so I know everything is going there, even when I set each VPN connection like:
Connection 1:
DNS Settings: Split DNS
Servers: 192.170.20.0/1, server1.rds.amazonaws.com
and
Connection 2:
DNS Settings: Split DNS
Servers: 192.120.15.0/1, server2.rds.amazonaws.com
Please don't laugh too much about my question.... and your time and help is greatly appreciated.
Regards,
Juan Luna
Hi Juan,
It sounds likely both are either set to route all traffic through them, or they're both using the same IP ranges for the VPN subnet, so it results in a route clash.
You should make sure that both servers are using a different IP range internally (e.g. not both on 10.8.0.x etc.), and that they're only pushing out the routes needed to access the subnets your SSH server/s are on (i.e. don't push redirect-gateway if not needed).
Cheers,
James
It sounds likely both are either set to route all traffic through them, or they're both using the same IP ranges for the VPN subnet, so it results in a route clash.
You should make sure that both servers are using a different IP range internally (e.g. not both on 10.8.0.x etc.), and that they're only pushing out the routes needed to access the subnets your SSH server/s are on (i.e. don't push redirect-gateway if not needed).
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts
Page 1 of 1