mandarjoshi

OK, I was able to get it to work.

It is not jumpbox as I thought. It's regular ssh port forwarding.

We ssh to the jumpbox system and forward the remote's port 22 to localhost:port_x. <~~ This can be done via ssh tunnel or ssh port forward vault entry.

And from another ssh session, we ssh to localhost:port_x.

Is this correct?

Also, what is the difference between ssh tunnel and ssh port forward vault entry?

The only difference I could see is that ssh tunnel entry can create only 1 port tunnel and port forward entry can create more.

I meant an SSH Jump host.

For ssh connections, I think it's more common to use ssh jump hosts than RDP jump hosts. (But I may be wrong.)

For ssh port forward, when I click VPN/Tunnel/Gateway, in the VPN type, it only allows "MSFT RDP gateway" as the option.

All other options show an error message "This mode is not supported."

I am using android version of RDM. Build # 2023.2.2.5.

Thanks!

To give you some more context:

When I launch ngrok to expose my local TCP port to the internet, it gives me a random hostname (depending on region and server load) and a random port (always random).

From a wrapper script, I push that data to my google spreadsheet (via app script) and to my AWS dynamodb (via a lambda).

From my ssh client system, I read these hostname+port combos and initiate a connection to it, instead of fixed IP and port 22.

From RDM, I have to update the hostname+port manually. So, I was wondering if it is possible to automate it from RDM itself.

A single button to update all dynamic hosts will be nice; or refresh all the dynamic hosts at app start.

I would leave it to you whether you want to add host+port as a combo to the vault or separately, that can be referenced in ssh and other vault entries.

Thank you once again.

I use ngrok (and other similar solutions) to expose my local server behind NAT over to the internet.

The hostname and the port it allocates are dynamic.

Can we have support for dynamic hostname/ports?

As an example,

The hostname/port can be obtained from some fixed web service like google app script or aws lambda.

POST to https://script.google.com/macros/something/exec? with some auth and some POST data will return the hostname/port in the response body.

Use that hostname+port for the SSH connection from RDM.

I suggested the web service POST option because it will be more generic than hard-coded to ngrok or jprq.

Can we have support for jumphost for SSH port forward?

Also, can we have the jump host settings inherited from an existing ssh entry?

e.g.

Vault Entry 1:

Connect to host1 - with username, password, private key etc.

Vault Entry 2:

Connect to host2 - with username, password, private key etc and jumphost = Vault entry1.

(Instead of specifying the ssh details separately)

Then maybe we would also be able to chain the Jumphosts.