Welcome to the VanDyke Software Forums

rguente · #1 01-20-2015, 03:58 AM

Hi,
I use jumphosts with portforwarding to access our hosts via ssh.
When I'm connected to several routers and then send a command to them via "Send Commands to All Sessions" in the Chat window, it's sent also to the (LINUX-) Jumphost which doesn't really understand Cisco-/Juniper-commands.
Would it be possible to add a feature which allows me to deny input from the Chat window to the jumphost?

bgagnon · #2 01-20-2015, 08:16 AM

Hello rguente,

What version of SecureCRT are you using?

On what platform/operating system?

So are you saying you have jumphost session, in addition to Connection_to_Cisco session(s) opened in tabs?

If so, since version 6.0, SecureCRT has had the ability to lock tabs. Locked tabs do not receive commands. You lock the tab by "right-clicking" the tab and choosing Lock Session... (you also have the option of entering a password). You should see a lock icon next to any locked sessions and can similarly unlock them from the tab's context menu.

rguente · #3 01-21-2015, 12:42 AM

Hi Brenda,

Thank you for the hint!

I've tested and it works fine. But much better would be a check-box in the Session-Options to achieve this per default once the (auto) session is started.
I use actually Version 7.2.6.

Best regards,
Robert

bgagnon · #4 01-21-2015, 08:45 AM

Hi Robert,

I would be happy to make the desired feature request, but have you investigated if this new functionality (added in v7.1) will work in your environment?

Changes in SecureCRT 7.1 (Beta 1) -- February 26, 2013
------------------------------------------------------

New features:

Added support for dependent sessions so that a connection can be made to a jump host or SSH gateway before the session is connected.

It does require that the jumphost server supports dynamic port forwarding.

With this method you would only have the tab to the end device so the jumphost session would not even be in play for receiving commands (that session is used in the firewall configuration in the Connection_to_Cisco session). Additional info on the use of the new functionality is found in this post.