Create one "Jump host" and assign to multiple connections

Implemented

Create one "Jump host" and assign to multiple connections

avatar
IsaacM
Disabled

Is there a way to create a SSH "jump host" and then assign it to SSH connections that require a jump host? I find it odd that you're required to specify the jump host IP address, login and password for each and every connection that requires a jump host. What am I missing?

Thanks

All Comments (25)

avatar
Jeff Dagenais

Hello,

I think you mean SSH Tunnel when you mentioned SSH Jump Host right?

If it's the case, I think the solution you are looking for is in this blog

https://blog.devolutions.net/2016/10/how-to-configure-ssh-tunnel-in-remote-desktop-manager

Best regards,

Jeff Dagenais

avatar
IsaacM
Disabled

I was under the mistaken impression "jump host" and "SSH Tunnel" were synonymous. You are correct, I'm referring to an SSH tunnel. The blog article provides instructions on how to tunnel to a remote host using the local port forwarding method. This method works well if you only need to tunnel traffic to single host. If you need to tunnel traffic to multiple hosts then this method quickly becomes an administrative nightmare.

I'm looking for a feature like this in RDM: https://blog.royalapplications.com/2015/04/21/new-feature-secure-gateway-ssh-tunnels/

I'd like to create one SSH tunnel object and then reference that object for any connection that can be reached via that particular SSH tunnel. Is something like this possible? I assume I'd have to use the dynamic ssh tunnel option somehow.

avatar
Jeff Dagenais

Hello,

Indeed, what you are looking for is available in RDM and explain in the blog above.

After creating the SSH Tunnel session, go in VPN section of you entry and configure it like the following:

This should do the trick.

Best regards,

Jeff Dagenais

avatar
IsaacM
Disabled

Thanks for the reply. Please correct me if I am wrong but specifying a session in VPN/SSH/Gateway ---> settings tab as mentioned in your previous message makes RDM auto-start the specified SSH tunnel prior to starting the session. That's it. It doesn't mean "Route this session through the specified SSH tunnel." It's a shortcut to auto-connect the tunnel. Nothing more nothing less.

I think there is some confusion in regards to what I'm asking about. Assuming I have 30 servers behind a firewall and want to connect to said servers via an "ssh jump host/SSH tunnel" I would have to create 60 total entries using the instructions provided in that blog post.

30SSH-tunnel connections. One for each server

30 SSH connections pointed at 127.0.0.1

I have a hard time believing that this is the only method available to connect hosts via an SSH tunnel. If this is indeed how things work in RDM then there has been a gross oversight to say the least which I'd like to believe isn't the case.

Ideally I'd create ONE ssh tunnel entry with a type of dynamic or something and point all connections to use the SOCKS proxy created by that SSH tunnel. An added benefit of doing it this way is that my ssh server entries don't have to be pointed to an artificial IP address such as 127.0.0.1.

If you're unsure of what I'm trying to do please see: https://blog.royalapplications.com/2015/04/21/new-feature-secure-gateway-ssh-tunnels/

Thanks for your help on this.