<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Bypassing corporate firewall with reverse ssh port forwarding</title>
	<atom:link href="http://toic.org/2009/01/18/reverse-ssh-port-forwarding/feed/" rel="self" type="application/rss+xml" />
	<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/</link>
	<description>Think shell</description>
	<lastBuildDate>Fri, 23 Jul 2010 17:58:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: thehidden</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-629</link>
		<dc:creator>thehidden</dc:creator>
		<pubDate>Fri, 23 Jul 2010 17:58:13 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-629</guid>
		<description>thank you for the good howto. i tried your idea with the reverse tunnel and every think works find. except of create an additional dynamic tunnel als socks proxy. can you explain please, how to do that? the tunnel is up, but no http traffic flows through. :-(

kind regards 
thehidden</description>
		<content:encoded><![CDATA[<p>thank you for the good howto. i tried your idea with the reverse tunnel and every think works find. except of create an additional dynamic tunnel als socks proxy. can you explain please, how to do that? the tunnel is up, but no http traffic flows through. <img src='http://toic.org/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
<p>kind regards<br />
thehidden</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Branko</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-623</link>
		<dc:creator>Branko</dc:creator>
		<pubDate>Tue, 25 May 2010 10:59:46 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-623</guid>
		<description>You should set &quot;GatewayPorts clientspecified&quot; in /etc/ssh/sshd_config not in /etc/ssh/ssh_config

/etc/ssh/ssh_config is config for ssh client and /etc/ssh/sshd_config is config for ssh server running on that machine.</description>
		<content:encoded><![CDATA[<p>You should set &#8220;GatewayPorts clientspecified&#8221; in /etc/ssh/sshd_config not in /etc/ssh/ssh_config</p>
<p>/etc/ssh/ssh_config is config for ssh client and /etc/ssh/sshd_config is config for ssh server running on that machine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Connectiong two seperate LANs with reverse SSH &#124; Bijan Hoomand</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-622</link>
		<dc:creator>Connectiong two seperate LANs with reverse SSH &#124; Bijan Hoomand</dc:creator>
		<pubDate>Mon, 24 May 2010 18:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-622</guid>
		<description>[...] toic, reverse ssh port forwarding [...]</description>
		<content:encoded><![CDATA[<p>[...] toic, reverse ssh port forwarding [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bijan</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-621</link>
		<dc:creator>bijan</dc:creator>
		<pubDate>Sat, 22 May 2010 07:59:37 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-621</guid>
		<description>Branko, this is a great post, thank you. However I have the same issue as Justin. Let&#039;s say I have a server (the middle man) with an IP address of 174.2.2.2, from my office box, I run:

ssh -R 178.2.2.2:1200:localhost:22 bijan@178.2.2.2

It connects with no problem. I also put &quot;GatewayPorts clientspecified&quot; in /etc/ssh/ssh_config. When I issue &quot;netstat -an &#124; grep LISTEN&quot;, I see it&#039;s listening on port 1200 for 127.0.0.1

The problem as Justin mentioned is that when I issue:

ssh -p 1200 officeUser@178.2.2.2

I get the following error: &quot;ssh: connect to host 178.2.2.2 port 1200: Connection refused&quot;. However if I ssh into 178.2.2.2 (to port 22 with a user on it) and then issue:

ssh -p 1200 officeUser@localhost

It&#039;s no problem, I login like a charm! I should say I disabled iptables, so, is it really a filtering problem or something wrong with me?</description>
		<content:encoded><![CDATA[<p>Branko, this is a great post, thank you. However I have the same issue as Justin. Let&#8217;s say I have a server (the middle man) with an IP address of 174.2.2.2, from my office box, I run:</p>
<p>ssh -R 178.2.2.2:1200:localhost:22 bijan@178.2.2.2</p>
<p>It connects with no problem. I also put &#8220;GatewayPorts clientspecified&#8221; in /etc/ssh/ssh_config. When I issue &#8220;netstat -an | grep LISTEN&#8221;, I see it&#8217;s listening on port 1200 for 127.0.0.1</p>
<p>The problem as Justin mentioned is that when I issue:</p>
<p>ssh -p 1200 officeUser@178.2.2.2</p>
<p>I get the following error: &#8220;ssh: connect to host 178.2.2.2 port 1200: Connection refused&#8221;. However if I ssh into 178.2.2.2 (to port 22 with a user on it) and then issue:</p>
<p>ssh -p 1200 officeUser@localhost</p>
<p>It&#8217;s no problem, I login like a charm! I should say I disabled iptables, so, is it really a filtering problem or something wrong with me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links 15/3/2010: CrossOver Linux, Tim Bray Joins Google &#124; Boycott Novell</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-609</link>
		<dc:creator>Links 15/3/2010: CrossOver Linux, Tim Bray Joins Google &#124; Boycott Novell</dc:creator>
		<pubDate>Mon, 15 Mar 2010 20:03:56 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-609</guid>
		<description>[...] Bypassing corporate firewall with reverse ssh port forwarding [...]</description>
		<content:encoded><![CDATA[<p>[...] Bypassing corporate firewall with reverse ssh port forwarding [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Rishøj</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-597</link>
		<dc:creator>Christian Rishøj</dc:creator>
		<pubDate>Fri, 05 Mar 2010 17:33:35 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-597</guid>
		<description>Excellent post! Thorough, explanatory and extremely useful. You saved the day!</description>
		<content:encoded><![CDATA[<p>Excellent post! Thorough, explanatory and extremely useful. You saved the day!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SSH port forwarding &#124; - [ t o i c . o r g ] -</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-588</link>
		<dc:creator>SSH port forwarding &#124; - [ t o i c . o r g ] -</dc:creator>
		<pubDate>Tue, 16 Feb 2010 13:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-588</guid>
		<description>[...] one of my previous post I made a tutorial how to bypass corporate firewalls and gain access into your office computer. It work well if you are at your home and you need ssh [...]</description>
		<content:encoded><![CDATA[<p>[...] one of my previous post I made a tutorial how to bypass corporate firewalls and gain access into your office computer. It work well if you are at your home and you need ssh [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reverse ssh port forwarding &#171; Linux notes</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-587</link>
		<dc:creator>Reverse ssh port forwarding &#171; Linux notes</dc:creator>
		<pubDate>Sun, 14 Feb 2010 15:07:11 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-587</guid>
		<description>[...] via Reverse ssh port forwarding &#124; &#8211; [ t o i c . o r g ] -. [...]</description>
		<content:encoded><![CDATA[<p>[...] via Reverse ssh port forwarding | &#8211; [ t o i c . o r g ] -. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Branko</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-583</link>
		<dc:creator>Branko</dc:creator>
		<pubDate>Mon, 25 Jan 2010 07:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-583</guid>
		<description>As far as I know this setup will not work for you in this way. 

If you reverse proxy the connections trough your home computer than all traffic will go trough that tunnel, and that beats the purpose of what your trying.</description>
		<content:encoded><![CDATA[<p>As far as I know this setup will not work for you in this way. </p>
<p>If you reverse proxy the connections trough your home computer than all traffic will go trough that tunnel, and that beats the purpose of what your trying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Branko</title>
		<link>http://toic.org/2009/01/18/reverse-ssh-port-forwarding/comment-page-1/#comment-582</link>
		<dc:creator>Branko</dc:creator>
		<pubDate>Mon, 25 Jan 2010 07:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://toic.org/?p=207#comment-582</guid>
		<description>What you need to do is make sure Gatewayports are set to clientspecified in /etc/ssh/sshd_config

On your vps run this command:

ssh -nNT -R 0.0.0.0:2222:localhost:22 username@localhost

Make sure you replace port 2222 with a port that is opened on your university, and replace username with your local vps username. 

After doing so make sure your vps firewall is permitting traffic on the port of your choice (2222 in this example).

Do a quick nestat -ntl on yoiur vps, and it should show something like this:

tcp        0      0 0.0.0.0:2222                0.0.0.0:*                   LISTEN</description>
		<content:encoded><![CDATA[<p>What you need to do is make sure Gatewayports are set to clientspecified in /etc/ssh/sshd_config</p>
<p>On your vps run this command:</p>
<p>ssh -nNT -R 0.0.0.0:2222:localhost:22 username@localhost</p>
<p>Make sure you replace port 2222 with a port that is opened on your university, and replace username with your local vps username. </p>
<p>After doing so make sure your vps firewall is permitting traffic on the port of your choice (2222 in this example).</p>
<p>Do a quick nestat -ntl on yoiur vps, and it should show something like this:</p>
<p>tcp        0      0 0.0.0.0:2222                0.0.0.0:*                   LISTEN</p>
]]></content:encoded>
	</item>
</channel>
</rss>
