#SSH TUNNEL LOG PASSWORD#

Not the password that goes with the SSH user, i.e. Next, and this is very important, enter the password that goes to the key you are using. The last command then releases the tunnel, the memory and the file. On this screen, enter the username for the SSH user you’re using. The first command sets up a tunnel and exits (instead of logging in), but stays in memory and records its activities in the named file. Here, /tmp/tunnel.B.to.C.control is an arbitrary name of file in a location where you can create a file. Ssh -O exit -S /tmp/tunnel.B.to.C.control address.of.B ssh -fNM -S /tmp/tunnel.B.to.C.control 7722:address.of.C:22 address.of.B If you don't have two terminals to work with, it is a bit more complex since you need a way to refer to the tunnel in order to be able to close it later. In the Port forwarding section, the Source Port is the source TCP/IP address you want assigned to your local host connection. Click on the path to reach Tunnels ( Connection > SSH >Tunnels ): 4. Do not save this yet we have to configure the ports for tunneling. Type the name you wish to use for the saved connection. Accept the prompt to continue with the connection. Open PuTTY.EXE, configure your host name, and select SSH for port. The default username for AKS nodes is azureuser. When you are done, just exit the second connection to leave C, then exit the first connection to deconstruct the tunnel. Create an SSH connection to the Windows Server node using the internal IP address. It is functionally equivalent to ssh address.of.C while the above tunnel exists. Will open a SSH connection to your local port 7722, which is being tunneled to C's 22. Then, in another terminal, ssh -X -p 7722 localhost At the same time, it will set up a tunnel between the current machine's port 7722 (can be any unused port over 1024, I arbitrarily selected 7722) and C's port 22 (the ssh port).

The easiest: ssh -L 7722:address.of.C:22 address.of.B

Ssh tunnel log