That’s correct. In that case you can only use the File Transfer session mode. We don’t support the Terminal session yet.
However you can leverage the Port forwarding session to connect to the remote ssh server even if this is not directly reachable from the Controller. This basically create a tunnel from the Controller to the Target.
You need to set these properties in the configuration (NOTE: you need to restart the Target):
- AllowTunnel
- AllowTunnelReverse
- TunnelList
For example if you set the properties like this:
AllowTunnel=yes
AllowTunnelReverse=no
TunnelList=ssh=tcp@127.0.0.1:22
and you switch to to the Port forwarding session

you can enable the tunnel by pressing on Start and by specifying a local (Controller) port to use for the tunnel (e.g: 2222).
Once the Tunnel is started when you connect to the local (Controller) port 2222 you will reach automatically the port 22 on the interface 127.0.0.1 on the Target (that’s because you set tcp@127.0.0.1:22
as TunnelList).
This can be very useful if the Target is on Internet or behind a NAT or a firewall and it can’t be reached directly.