<li>A: The server; this machine is behind a firewall that allows outgoing connections but doesn’t allow incoming.</li>
<li>B: The bounce host; this machine is unfirewalled.</li>
<li>C: The client.</li>
</ul>
<h3>Configuring B</h3>
<p>Some sshd configuration needs to be done on B before any of this will work. In the sshd_config file (/etc/ssh/sshd_config on Debian):</p>
<pre><code>AllowTcpForwarding yes
GatewayPorts yes
</code></pre>
<p>Remember to restart sshd after making changes (/etc/init.d/ssh restart).</p>
<h3>Building the Tunnel</h3>
<p>On A, run:</p>
<pre><code>ssh -g -n -R <port on B>:127.0.0.1:<port on A><address of B> sleep 999999
</code></pre>
<p>This will hang with no output; that’s the expected result.</p>
<p>You should now be able to connect to the port on B and be talking to A. To get this to restart if the connection dies, run it inside:</p>
<pre><code>while :; do <command>; done
</code></pre>
<p>As with all shell commands, put a “&” on the end to run it in the background.</p>
<h3>Tunnelling FTP</h3>
<p>Due to a trick in the FTP protocol, you can use this tunnelling arrangement but have FTP data connections go directly from A to C, without touching B. This only works with so-called “active” FTP (using the PORT command instead of PASV). C must also be unfirewalled for this to work.</p>
<p>The only thing you’ll need to change is the FTP server configuration. In proftpd.conf, add:</p>
<pre><code>AllowForeignAddress on
</code></pre>
<p>For pure-ftpd, run it with the “-w” commandline flag, or with a file named “AllowUserFXP” and a contents of “on” if you’re using pure-ftpd-wrapper.</p>
