Linux: SSH tips and tricks - Revision history

David: /* Passwordless access */

2024-09-06T11:53:43Z

Passwordless access

David at 10:25, 20 November 2017

2017-11-20T10:25:49Z

David: /* Multi Forward SSH for VNC */

2017-11-20T10:24:51Z

Multi Forward SSH for VNC

David at 16:35, 18 May 2016

2016-05-18T16:35:10Z

David: /* Setup a reverse tunnel */

2014-12-04T16:05:19Z

Setup a reverse tunnel

David: /* SSH Tunnelling */

2013-01-02T22:34:18Z

SSH Tunnelling

David at 22:28, 2 January 2013

2013-01-02T22:28:17Z

David at 10:30, 14 November 2012

2012-11-14T10:30:41Z

David: Created page with "== SSH Tunnelling == In this example I wanted to access the web interface for our cluster on port 8080 which was blocked # ssh -L [local port]:localsystem:[remote port..."

2012-11-14T10:28:37Z

Created page with "== SSH Tunnelling == In this example I wanted to access the web interface for our cluster on port 8080 which was blocked <syntaxhighlight> # ssh -L [local port]:localsystem:[remote port..."

New page

== SSH Tunnelling ==
In this example I wanted to access the web interface for our cluster on port 8080 which was blocked

<syntaxhighlight>
# ssh -L [local port]:localsystem:[remote port] remote-system
[david@localdesktop]$ ssh -L 8080:localhost:8080 bostonhpc.co.uk
</syntaxhighlight>

Then i could point the browser at http://localhost:8080 to access the PCM console

== Setup a reverse tunnel ==
In this example i want to create an ssh tunnel from a node in bostonlabs to viglen

<syntaxhighlight>
[viglen@amd-quad]$ ssh -R 2222:localhost:22 david@vhpchead.viglen.co.uk
</syntaxhighlight>

From the vhpchead node, I can then connect to my desktop node through port 2222
<syntaxhighlight>
[david@vhpchead]$ ssh -p2222 viglen@localhost
</syntaxhighlight>

← Older revision		Revision as of 11:53, 6 September 2024
Line 79:		Line 79:

	* Note: .ssh directory needs to have perms: 700 and the authorized_keys files needs to be 600		* Note: .ssh directory needs to have perms: 700 and the authorized_keys files needs to be 600
		+
		+	== Dodgy skyline forwarding for the BMC labs ==
		+	<pre>
		+	# ssh_config (set up on skyline vm)
		+	GatewayPorts yes
		+
		+	# ip adds lo on the host - (on the skyline instance)
		+	ip addr add 10.10.12.10/32 dev lo
		+
		+	# revese tunnel (in a screen)
		+	ssh -R 0.0.0.0:5000:10.10.12.10:5000 -R 0.0.0.0:9696:10.10.12.10:9696 -R 0.0.0.0:8000:10.10.12.10:8000 -R 0.0.0.0:9001:10.10.12.10:9001 -R 0.0.0.0:8776:10.10.12.10:8776 -R 0.0.0.0:8774:10.10.12.10:8774 -R 0.0.0.0:8780:10.10.12.10:8780 -R 0.0.0.0:9311:10.10.12.10:9311 -R 0.0.0.0:9511:10.10.12.10:9511 -R 0.0.0.0:5050:10.10.12.10:5050 -R 0.0.0.0:8000:10.10.12.10:8000 -R 0.0.0.0:9292:10.10.12.10:9292 -R 0.0.0.0:9001:10.10.12.10:9001 -R 0.0.0.0:8004:10.10.12.10:8004 -R 0.0.0.0:6385:10.10.12.10:6385 -R 0.0.0.0:8780:10.10.12.10:8780 -R 0.0.0.0:9876:10.10.12.10:9876 root@185.93.31.142 -vvv
		+
		+	</pre>

@@ Line 34: / Line 34: @@
 $ ssh -L 9999:localhost:9999 bl ssh -L 9999:localhost:5901 -N keele
 </syntaxhighlight>
 == Passwordless access ==
 * Generate the SSH Keys

@@ Line 29: / Line 29: @@
 </syntaxhighlight>
 == Passwordless access ==
 * Generate the SSH Keys

@@ Line 9: / Line 9: @@
 Then i could point the browser at http://localhost:8080 to access the PCM console
-Another example: I wanted to access another systems ipmi web interface which was accessible from the headnode:
+Another example: I wanted to access another systems ipmi web interface which was accessible from the headnode, needed both 443 and 80 to be forwarded
-<snip>
+<syntaxhighlight>
 $ ssh -L 8080:10.9.2.99:80 bostonhpc.co.uk
 # then point local web browser at http://localhost:8080
-</snip>
+</syntaxhighlight>
 == Setup a reverse tunnel ==

← Older revision		Revision as of 22:28, 2 January 2013
Line 8:		Line 8:

	Then i could point the browser at http://localhost:8080 to access the PCM console		Then i could point the browser at http://localhost:8080 to access the PCM console
		+
		+	Another example: I wanted to access another systems ipmi web interface which was accessible from the headnode:
		+	<snip>
		+	$ ssh -L 8080:10.9.2.99:80 bostonhpc.co.uk
		+	# then point local web browser at http://localhost:8080
		+	</snip>

	== Setup a reverse tunnel ==		== Setup a reverse tunnel ==

@@ Line 21: / Line 21: @@
 <syntaxhighlight>
-[viglen@amd-quad]$ ssh -R 2222:localhost:22 david@vhpchead.viglen.co.uk
+[viglen@amd-quad]$ ssh -R 2222:localhost:22 user@bostonhpc.co.uk
 </syntaxhighlight>

← Older revision		Revision as of 10:30, 14 November 2012
Line 20:		Line 20:
	[david@vhpchead]$ ssh -p2222 viglen@localhost		[david@vhpchead]$ ssh -p2222 viglen@localhost
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	== Passwordless access ==
		+	* Generate the SSH Keys
		+
		+	<syntaxhighlight>
		+	ssh-keygen -t rsa
		+	</syntaxhighlight>
		+
		+	* Copy the RSA public key to the remote host
		+
		+	<syntaxhighlight>
		+	cat ~/.ssh/id_rsa.pub \| ssh user@remote.machine.com 'cat >> .ssh/authorized_keys'
		+
		+	# Alternatively: (but not as pretty!)
		+	ssh-copy-id user@remotehost
		+	</syntaxhighlight>
		+
		+	* Note: .ssh directory needs to have perms: 700 and the authorized_keys files needs to be 600