SSH Port forward connects to target instead of localhost

Published 10 years ago

I'm doing a new evaluation of RDM. I want to tunnel SSH connections through an SSH tunnel to have a central break-out point within the network for management connections.

I set RDM up as follows to allow for a single 'gateway' connection to manage multiple remote machines.

Connection entry

Outgoing tunnel settings:

Next I set up an SSH Shell connection profile:

VPN/SSH/Gateway

Now when I try to connect it establishes the tunnel to the jump host:

Then it attempts to connect to the target machine (which should by accessible through 127.0.0.1:41621):

So RDM is connecting to the target host instead of the tunnel. If I configure More > Alternate Host > Prompt for selection and add 127.0.0.1 to the list it works, but this seems a bit of a workaround for a bug.

Can you confirm whether I'm doing it wrong or this is just a bug?

edit: this appears to overlap a bit with the following topic: https://forum.devolutions.net/topic26515-ssh-tunnel-vpn-entry--dynamic-port-usage.aspx

All Comments (2)

Maurice Côté

Published 10 years ago

Hello,

I do not see in your structure where you have a parent, therefore why you are using PARENT_HOST.

There are two entries in play in a normal scenario, the Jump host, (in this case a SSH Tunnel) and a SSH Session.

The tunnel should take care of reaching the final destination, therefore the SSH Session connects to 127.0.0.1, it doesn't know anything about the remote host.

The full instructions can be found on How-To > How to Setup a SSH Tunnel

Best regards,

Maurice

m.schouren

Published 10 years ago

I am using the parent host feature because I use 1 gateway entry for multiple SSH sessions. The instructions that you link are for a 1:1 setup (1 tunnel for 1 session, where I want a single tunnel entry for multiple actual sessions). This functionality is described in https://forum.devolutions.net/topic23592-multiple-rdp-hosts-via-single-ssh-tunnel.aspx :