SecureShellTunneling - Revision history

Vsammeta: Added alt text to all the images

2026-03-23T17:45:40Z

Added alt text to all the images

← Older revision		Revision as of 17:45, 23 March 2026
Line 23:		Line 23:
	All modern versions of Windows can use the OpenSSH method mentioned in the previous section. Windows users can also achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under "Connection>SSH>Tunnels".		All modern versions of Windows can use the OpenSSH method mentioned in the previous section. Windows users can also achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under "Connection>SSH>Tunnels".

	[[Image:PuTTYWin7Tunnel.png]]		[[Image:PuTTYWin7Tunnel.png \|alt=PuTTY config screen on Connection/SSH/Tunnels menu]]

	This example will create a local port '''8889''' that is attached to the remote host '''clipsm301.umiacs.umd.edu''' on its port '''8000'''.		This example will create a local port '''8889''' that is attached to the remote host '''clipsm301.umiacs.umd.edu''' on its port '''8000'''.
Line 41:		Line 41:
	In PuTTY under '''Sessions''' set the Host Name:		In PuTTY under '''Sessions''' set the Host Name:

	[[Image:Putty1.png]]		[[Image:Putty1.png \|alt=Setting a host name in PuTTY config Session menu]]

	Then under <code>Connection > SSH > Tunnels</code> enter a port number and set the type of forwarding to "Dynamic" and press add:		Then under <code>Connection > SSH > Tunnels</code> enter a port number and set the type of forwarding to "Dynamic" and press add:

	[[Image:Putty2.png]]		[[Image:Putty2.png \|alt=Entering a port and configuring it in the Tunneling menu of the Config screen]]

	Click Open and log into the host.		Click Open and log into the host.
Line 62:		Line 62:
	'''NOTE:''' this will continue to send all browser traffic through your SSH tunnel until the configuration is reverted. The SSH connection must be established for traffic to pass through to the destination network. Firefox has a very useful plugin called "FoxyProxy" that allows conditional proxies to be set up, if you're interested in adding some intelligence/complexity to your proxy configuration.		'''NOTE:''' this will continue to send all browser traffic through your SSH tunnel until the configuration is reverted. The SSH connection must be established for traffic to pass through to the destination network. Firefox has a very useful plugin called "FoxyProxy" that allows conditional proxies to be set up, if you're interested in adding some intelligence/complexity to your proxy configuration.

	[[Image:FF_Proxy_1.png\|400px]] [[Image:FF_Proxy_2.png\|400px]]		[[Image:FF_Proxy_1.png\|400px \|alt=Firefox network config menu]] [[Image:FF_Proxy_2.png\|400px \|alt=Setting up HTTP proxy in Firefox network settings]]

Mbaney at 16:19, 3 September 2025

2025-09-03T16:19:35Z

← Older revision		Revision as of 16:19, 3 September 2025
Line 5:		Line 5:
	<ul>		<ul>
	<li>This example will create a local port 9999 that will be forwarded to the remote host webserver.umiacs.umd.edu and its port 8000 through the host nexusgroup.umiacs.umd.edu.		<li>This example will create a local port 9999 that will be forwarded to the remote host webserver.umiacs.umd.edu and its port 8000 through the host nexusgroup.umiacs.umd.edu.
	<pre>ssh -NfL 9999:webserver.umiacs.umd.edu:8000 <USERNAME>@nexusgroup.umiacs.umd.edu</pre>		<pre>ssh -NfL localhost:9999:webserver.umiacs.umd.edu:8000 <USERNAME>@nexusgroup.umiacs.umd.edu</pre>
	</li>		</li>

	<li>This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop \|RDP]] client like Windows through the host nexusgroup.umiacs.umd.edu		<li>This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop \|RDP]] client like Windows through the host nexusgroup.umiacs.umd.edu
	<pre>ssh -NfL 13389:my-desktop.ad.umiacs.umd.edu:3389 <USERNAME>@nexusgroup.umiacs.umd.edu</pre>		<pre>ssh -NfL localhost:13389:my-desktop.ad.umiacs.umd.edu:3389 <USERNAME>@nexusgroup.umiacs.umd.edu</pre>
	</li>		</li>

	<li>The following example outlines how to use SSH tunnel for printing to the UMIACS CUPS server.		<li>The following example outlines how to use SSH tunnel for printing to the UMIACS CUPS server.
	<pre>ssh <USERNAME>@nexusgroup.umiacs.umd.edu -T -N -L 3631:print.umiacs.umd.edu:631</pre>		<pre>ssh <USERNAME>@nexusgroup.umiacs.umd.edu -T -N -L localhost:3631:print.umiacs.umd.edu:631</pre>
	</li>		</li>
	<li>Once the tunnel is established you can follow the normal [[Printing \| Printing]] instructions, substituting 'print.umiacs.umd.edu~~' for 'localhost:3631~~', or print via the a command such as the following:		<li>Once the tunnel is established you can follow the normal [[Printing \| Printing]] instructions, substituting 'localhost:3631' in place of 'print.umiacs.umd.edu', or print via the a command such as the following:
	<pre>lpr -H ~~127.0.0.1~~:3631 -P <PRINTER NAME> <FILENAME></pre>		<pre>lpr -H localhost:3631 -P <PRINTER NAME> <FILENAME></pre>
	</li>		</li>
	</ul>		</ul>

Mbaney at 15:58, 3 February 2025

2025-02-03T15:58:07Z

← Older revision		Revision as of 15:58, 3 February 2025
Line 21:		Line 21:

	===PuTTY===		===PuTTY===
	Windows users can achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under "Connection>SSH>Tunnels".		All modern versions of Windows can use the OpenSSH method mentioned in the previous section. Windows users can also achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under "Connection>SSH>Tunnels".

	[[Image:PuTTYWin7Tunnel.png]]		[[Image:PuTTYWin7Tunnel.png]]
Line 37:		Line 37:

	===PuTTY===		===PuTTY===
	Windows users can tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.		All modern versions of Windows can use the OpenSSH method mentioned in the previous section. Windows users can also tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.

	In PuTTY under '''Sessions''' set the Host Name:		In PuTTY under '''Sessions''' set the Host Name:

Mbaney: /* OpenSSH */

2025-02-03T15:55:25Z

OpenSSH

← Older revision		Revision as of 15:55, 3 February 2025
Line 2:		Line 2:

	===OpenSSH===		===OpenSSH===
	~~When you want~~ to ~~just~~ forward a specific port ~~locally~~ to a remote port with Linux or ~~macOS systems~~.		You can use OpenSSH port forwarding to forward a specific port on your local machine to a remote port on a UMIACS-supported machine with any modern version of a Linux, macOS, or Windows system.
	<ul>		<ul>
	<li>This example will create a local port 9999 that will be forwarded to the remote host webserver.umiacs.umd.edu and its port 8000 through the host nexusgroup.umiacs.umd.edu.		<li>This example will create a local port 9999 that will be forwarded to the remote host webserver.umiacs.umd.edu and its port 8000 through the host nexusgroup.umiacs.umd.edu.

Mbaney at 15:52, 3 February 2025

2025-02-03T15:52:30Z

← Older revision		Revision as of 15:52, 3 February 2025
Line 9:		Line 9:

	<li>This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop \|RDP]] client like Windows through the host nexusgroup.umiacs.umd.edu		<li>This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop \|RDP]] client like Windows through the host nexusgroup.umiacs.umd.edu
	<pre>ssh -L 13389:my-desktop.ad.umiacs.umd.edu:3389 <USERNAME>@nexusgroup.umiacs.umd.edu</pre>		<pre>ssh -NfL 13389:my-desktop.ad.umiacs.umd.edu:3389 <USERNAME>@nexusgroup.umiacs.umd.edu</pre>
	</li>		</li>

Mbaney at 15:24, 3 January 2025

2025-01-03T15:24:10Z

← Older revision		Revision as of 15:24, 3 January 2025
Line 4:		Line 4:
	When you want to just forward a specific port locally to a remote port with Linux or macOS systems.		When you want to just forward a specific port locally to a remote port with Linux or macOS systems.
	<ul>		<ul>
	<li>This example will create a local port 9999 that will be forwarded to the remote host webserver.umiacs.umd.edu and its port 8000 through the host ~~nexusclip00~~.umiacs.umd.edu.		<li>This example will create a local port 9999 that will be forwarded to the remote host webserver.umiacs.umd.edu and its port 8000 through the host nexusgroup.umiacs.umd.edu.
	<pre>ssh -NfL 9999:webserver.umiacs.umd.edu:8000 ~~nexusclip00~~.umiacs.umd.edu</pre>		<pre>ssh -NfL 9999:webserver.umiacs.umd.edu:8000 <USERNAME>@nexusgroup.umiacs.umd.edu</pre>
	</li>		</li>

	<li>This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop \|RDP]] client like Windows through the host ~~nexusclip00~~.umiacs.umd.edu		<li>This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop \|RDP]] client like Windows through the host nexusgroup.umiacs.umd.edu
	<pre>ssh -L 13389:my-desktop.ad.umiacs.umd.edu:3389 ~~nexusclip00~~.umiacs.umd.edu</pre>		<pre>ssh -L 13389:my-desktop.ad.umiacs.umd.edu:3389 <USERNAME>@nexusgroup.umiacs.umd.edu</pre>
	</li>		</li>

	<li>The following example outlines how to use SSH tunnel for printing to the UMIACS CUPS server.		<li>The following example outlines how to use SSH tunnel for printing to the UMIACS CUPS server.
	<pre>ssh $<USERNAME>@~~nexusclip00~~.umiacs.umd.edu -T -N -L 3631:print.umiacs.umd.edu:631</pre>		<pre>ssh <USERNAME>@nexusgroup.umiacs.umd.edu -T -N -L 3631:print.umiacs.umd.edu:631</pre>
	</li>		</li>
	<li>Once the tunnel is established you can follow the normal [[Printing \| Printing]] instructions ~~substitution~~ 'print.umiacs.umd.edu' for 'localhost:3631', or print via the a command such as the following:		<li>Once the tunnel is established you can follow the normal [[Printing \| Printing]] instructions, substituting 'print.umiacs.umd.edu' for 'localhost:3631', or print via the a command such as the following:
	<pre>lpr -H 127.0.0.1:3631 -P $<PRINTER NAME> $<FILENAME></pre>		<pre>lpr -H 127.0.0.1:3631 -P <PRINTER NAME> <FILENAME></pre>
	</li>		</li>
	</ul>		</ul>
Line 32:		Line 32:
	[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy. Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command.		[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy. Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command.

	<pre>ssh -ND 7777 ~~nexusclip00~~.umiacs.umd.edu</pre>		<pre>ssh -ND 7777 nexusgroup.umiacs.umd.edu</pre>

	Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy. This can have performance implications.		Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy. This can have performance implications.

Mbaney at 20:11, 6 June 2023

2023-06-06T20:11:22Z

← Older revision		Revision as of 20:11, 6 June 2023
Line 2:		Line 2:

	===OpenSSH===		===OpenSSH===

	When you want to just forward a specific port locally to a remote port with Linux or macOS systems.		When you want to just forward a specific port locally to a remote port with Linux or macOS systems.
	<ul>		<ul>
Line 22:		Line 21:

	===PuTTY===		===PuTTY===

	Windows users can achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under "Connection>SSH>Tunnels".		Windows users can achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under "Connection>SSH>Tunnels".

Line 32:		Line 30:

	===OpenSSH===		===OpenSSH===

	[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy. Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command.		[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy. Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command.

Line 40:		Line 37:

	===PuTTY===		===PuTTY===

	Windows users can tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.		Windows users can tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.

Line 57:		Line 53:

	=== Example: SOCKS proxy, Browser configuration ===		=== Example: SOCKS proxy, Browser configuration ===
	~~[[Image:FF_Proxy_1.png\|thumb\|]] [[Image:FF_Proxy_2.png\|thumb\|]]~~
	There are too many variations here to cover them all, but they all follow the same general pattern and the following example should be generally applicable. We'll use Firefox for this example. Screenshots are from Firefox 37.0.2.		There are too many variations here to cover them all, but they all follow the same general pattern and the following example should be generally applicable. We'll use Firefox for this example. Screenshots are from Firefox 37.0.2.

	* Under <code>Preferences > Advanced > Network > Connection > Settings...</code>, choose <code>Manually proxy configuration:</code>.		# Under <code>Preferences > Advanced > Network > Connection > Settings...</code>, choose <code>Manually proxy configuration:</code>.
	* Enter <code>127.0.0.1</code> for the proxy.		# Enter <code>127.0.0.1</code> for the proxy.
	* Enter the port you chose earlier for dynamic forwarding (7777 in the example above).		# Enter the port you chose earlier for dynamic forwarding (7777 in the example above).
	* Check <code>Use this proxy server for all protocols</code>, and then click OK.		# Check <code>Use this proxy server for all protocols</code>, and then click OK.

	'''NOTE:''' this will continue to send all browser traffic through your SSH tunnel until the configuration is reverted. The SSH connection must be established for traffic to pass through to the destination network. Firefox has a very useful plugin called "FoxyProxy" that allows conditional proxies to be set up, if you're interested in adding some intelligence/complexity to your proxy configuration.		'''NOTE:''' this will continue to send all browser traffic through your SSH tunnel until the configuration is reverted. The SSH connection must be established for traffic to pass through to the destination network. Firefox has a very useful plugin called "FoxyProxy" that allows conditional proxies to be set up, if you're interested in adding some intelligence/complexity to your proxy configuration.

			[[Image:FF_Proxy_1.png\|400px]] [[Image:FF_Proxy_2.png\|400px]]

Mbaney: /* Example: SOCKS proxy, Browser configuration */

2023-06-06T20:10:05Z

Example: SOCKS proxy, Browser configuration

← Older revision		Revision as of 20:10, 6 June 2023
Line 58:		Line 58:
	=== Example: SOCKS proxy, Browser configuration ===		=== Example: SOCKS proxy, Browser configuration ===
	[[Image:FF_Proxy_1.png\|thumb\|]] [[Image:FF_Proxy_2.png\|thumb\|]]		[[Image:FF_Proxy_1.png\|thumb\|]] [[Image:FF_Proxy_2.png\|thumb\|]]
	There are too many variations here to cover them all, but they all follow the same general pattern and the following example should be generally applicable. We'll use Firefox for this example. Screenshots are from FF 37.0.2		There are too many variations here to cover them all, but they all follow the same general pattern and the following example should be generally applicable. We'll use Firefox for this example. Screenshots are from Firefox 37.0.2.

	* Under <code> Preferences > Advanced > Network > Connection > Settings... </code>		* Under <code>Preferences > Advanced > Network > Connection > Settings...</code>, choose <code>Manually proxy configuration:</code>.
	* choose <code>Manually proxy configuration:</code>,		* Enter <code>127.0.0.1</code> for the proxy.
	* ~~enter~~ <code>127.0.0.1</code> for the proxy		* Enter the port you chose earlier for dynamic forwarding (7777 in the example above).
	* ~~enter~~ the port you chose earlier for dynamic forwarding (7777 in the example above.)		* Check <code>Use this proxy server for all protocols</code>, and then click OK.
	* Check <code>Use this proxy server for all protocols</code>, and then click OK.

	'''NOTE:''' this will continue to send all browser traffic through your SSH tunnel until the configuration is reverted. The SSH connection must be established for traffic to pass through to the destination network. Firefox has a very useful plugin called "FoxyProxy" that allows conditional proxies to be set up, if you're interested in adding some intelligence/complexity to your proxy configuration.		'''NOTE:''' this will continue to send all browser traffic through your SSH tunnel until the configuration is reverted. The SSH connection must be established for traffic to pass through to the destination network. Firefox has a very useful plugin called "FoxyProxy" that allows conditional proxies to be set up, if you're interested in adding some intelligence/complexity to your proxy configuration.

Jayid07: /* OpenSSH */

2022-04-25T17:11:31Z

OpenSSH

← Older revision		Revision as of 17:11, 25 April 2022
Line 35:		Line 35:
	[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy. Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command.		[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy. Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command.

	<pre>ssh -ND 7777 ~~openlab~~.umiacs.umd.edu</pre>		<pre>ssh -ND 7777 nexusclip00.umiacs.umd.edu</pre>

	Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy. This can have performance implications.		Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy. This can have performance implications.

Jayid07: /* Port Forwarding */

2022-04-25T17:11:01Z

Port Forwarding

← Older revision		Revision as of 17:11, 25 April 2022
Line 5:		Line 5:
	When you want to just forward a specific port locally to a remote port with Linux or macOS systems.		When you want to just forward a specific port locally to a remote port with Linux or macOS systems.
	<ul>		<ul>
	<li>This example will create a local port 9999 that will be forwarded to the remote host webserver.umiacs.umd.edu and its port 8000 through the host ~~openlab~~.umiacs.umd.edu.		<li>This example will create a local port 9999 that will be forwarded to the remote host webserver.umiacs.umd.edu and its port 8000 through the host nexusclip00.umiacs.umd.edu.
	<pre>ssh -NfL 9999:webserver.umiacs.umd.edu:8000 ~~openlab~~.umiacs.umd.edu</pre>		<pre>ssh -NfL 9999:webserver.umiacs.umd.edu:8000 nexusclip00.umiacs.umd.edu</pre>
	</li>		</li>

	<li>This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop \|RDP]] client like Windows through the host ~~openlab~~.umiacs.umd.edu		<li>This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop \|RDP]] client like Windows through the host nexusclip00.umiacs.umd.edu
	<pre>ssh -L 13389:my-desktop.ad.umiacs.umd.edu:3389 ~~openlab~~.umiacs.umd.edu</pre>		<pre>ssh -L 13389:my-desktop.ad.umiacs.umd.edu:3389 nexusclip00.umiacs.umd.edu</pre>
	</li>		</li>

	<li>The following example outlines how to use SSH tunnel for printing to the UMIACS CUPS server.		<li>The following example outlines how to use SSH tunnel for printing to the UMIACS CUPS server.
	<pre>ssh $<USERNAME>@~~openlab~~.umiacs.umd.edu -T -N -L 3631:print.umiacs.umd.edu:631</pre>		<pre>ssh $<USERNAME>@nexusclip00.umiacs.umd.edu -T -N -L 3631:print.umiacs.umd.edu:631</pre>
	</li>		</li>
	<li>Once the tunnel is established you can follow the normal [[Printing \| Printing]] instructions substitution 'print.umiacs.umd.edu' for 'localhost:3631', or print via the a command such as the following:		<li>Once the tunnel is established you can follow the normal [[Printing \| Printing]] instructions substitution 'print.umiacs.umd.edu' for 'localhost:3631', or print via the a command such as the following:
Line 28:		Line 28:

	This example will create a local port '''8889''' that is attached to the remote host '''clipsm301.umiacs.umd.edu''' on its port '''8000'''.		This example will create a local port '''8889''' that is attached to the remote host '''clipsm301.umiacs.umd.edu''' on its port '''8000'''.



	==SOCKS Proxy==		==SOCKS Proxy==