ProxyCommand in your SSH config.
Create an SSH configuration file in your home directory (unless you want to make this system-wide),
Host unibroker # Machine B definition (the broker)
Hostname 184.108.40.206 # Change this IP address to the address of the broker
User myusername # Change this default user accordingly
# (`user@unibroker` can overwrite it)
Host internalmachine # Machine A definition (the target host)
ProxyCommand ssh -q unibroker nc -q0 hostname.or.IP.address.internal.machine 22
Now you can reach Machine A directly using
Also note that now you have a single SSH host target name for it, you can use this in other applications as well. E.g.:
SCP to copy files.
scp somefile user@internalmachine:~/
In your GUI applications:
sftp://user@internalmachine/ as the location to browse on the machine.
KDE-based (Dolphin): use
hostname.or.IP.address.internal.machine and the port (
22) to the machine you like to reach as if you would from the
Depending on netcat versions on the unibroker host, the
-q0 option must be omitted. Regarding authentication; you're basically setting up two SSH connections from your workstation. This means both the unibroker host and the internalmachine host are verified/authenticated against one after another (for both keypair/password and host key verification).
This approach of the use of
ProxyCommand and 'netcat' is just one way to do it. I like this, because my SSH client talks directly to the target machine so that I can verify the host key from my client and I can use my public key authentication without using another key on the broker.
Host defines the start of a new host section.
Hostname is the target hostname or IP address of that host.
User is what you would provide as the user part in
ProxyCommand will be used as the pipe to the target machine. By using SSH to the first machine and directly setting up a simple 'netcat' (
nc) to the target from there, this is basically just a plaintext forward to the internal machine from the broker between those. The
-q options are to silence any output (just a personal preference).
Make sure you have netcat installed on the broker (usually available by default on Ubuntu) - either netcat-openbsd or netcat-traditional .
Note that you're still using SSH with encryption twice here. While the netcat channel is plaintext, your SSH client on your PC will set up another encrypted channel with the final target machine.