<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Firewall on ilikeorangutans</title><link>https://kuelzer.ca/tags/firewall/</link><description>Recent content in Firewall on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 12 Apr 2026 14:15:30 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/firewall/index.xml" rel="self" type="application/rss+xml"/><item><title>SSH (Remote) Tunnels</title><link>https://kuelzer.ca/posts/2011/01/02/ssh-remote-tunnels/</link><pubDate>Sun, 02 Jan 2011 12:36:58 -0400</pubDate><guid>https://kuelzer.ca/posts/2011/01/02/ssh-remote-tunnels/</guid><description>&lt;p&gt;Just figured out how SSH remote tunnels work and wanted to write it down.&lt;/p&gt;
&lt;p&gt;Nomenclature:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;[Local] Client&lt;/em&gt;: your local computer. In fact, if I say local, I mean the client.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;[Remote] Server&lt;/em&gt;: the server you connect to. If I say remote, I mean server.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="forward-tunnels"&gt;Forward Tunnels&lt;/h3&gt;
&lt;p&gt;Your standard tunnel, allows you to take a local port and redirect it to a remote port on the server:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;$ ssh -L REMOTEPORT:client:CLIENTPORT user@server
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Now, that by opening a tunnel in this way:&lt;/p&gt;</description></item></channel></rss>