SSH Tunnels with built-in SSH Shell

Hi,
I will assign the thread to André. He is the one that did the built-in ssh

Hi,

How did you created the SSH tunnel, with Putty or built-in SSH functions ?

Regards,
edited by asanscartier on 9/25/2014

Hey André,

Yes, I've built the tunnel with the built-in SSH functions (no PuTTY involved in creating the tunnel).
After the tunnel is created we are unable to use the built-in SSH Shell to go through it, yet we are able to go through it with an embedded PuTTY session.

Hi,
Do you mean that you are using Putty successfully with the RDM built-in tunnel or with Putty SSH integrated functions ?
Because our built-in Outgoing SSH tunnel is not supposed to support that behaviour yet. But we are using a third party for SSH features, it always possible that some changes occurred.
Regards,

Hi,

To create the tunnel I'm using RDM built-in SSH.
Add > Add Session > Telnet, SSH, Raw, rLogin.
In the drop down list I select "SSH".
In the Host I'm entering my remote Linux server IP address to create the tunnel on.
In the "Outgoing Tunnel Settings":
Local IP: 127.0.0.1
Port: Local port to bind to (i.e 7138)
Remote Host: IP of remote host to create tunnel to
Remote Port: 22

Then I create another Session as above, but instead of "SSH" I select "PuTTY", and enter host to connect: localhost, port: 7138. This way everything works as expected.
If instead of "PuTTY" I select "SSH Shell" with the same parameters it will just time out, unable to connect.

Hi,
Indeed you found a bug. If Putty works our SSH Shell should to.
It's now in our todo list. Meanwhile please use Putty instead.
Sorry for any inconvenience,

Thanks André,
As you suggested, we will use PuTTY session until its fixed.

Also, while at it, I would like to suggest adding the ability to set more than one tunnel per session settings.