<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Port Forwarding with SSH</title>
	<link>http://www.linux-mag.com/id/5104/</link>
	<description>Open Source, Open Standards</description>
	<pubDate>Sat, 22 Nov 2008 00:12:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: sys49152</title>
		<link>http://www.linux-mag.com/id/5104/#comment-866</link>
		<pubDate>Sun, 24 Feb 2008 16:42:15 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/5104/#comment-866</guid>
					<description>hmm, has anyone done an IP-tunnel (GRE) with this?
I'm looking for a solution which works with the commands 'ssh', 'ifconfig' and 'route'.
Any ideas?</description>
		<content:encoded><![CDATA[<p>hmm, has anyone done an IP-tunnel (GRE) with this?<br />
I&#8217;m looking for a solution which works with the commands &#8217;ssh&#8217;, &#8216;ifconfig&#8217; and &#8216;route&#8217;.<br />
Any ideas?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: raywang007@gmail.com</title>
		<link>http://www.linux-mag.com/id/5104/#comment-855</link>
		<pubDate>Thu, 21 Feb 2008 00:54:23 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/5104/#comment-855</guid>
					<description>well, I believe the other dynamic forwarding feature is more useful. ssh -D 8080 @, you literally set up a SOCKS5 proxy at port 8080 one your local computer, which then transfers data in the secure channel to your remote host, then to the entire world. You can then do a lot of things with this dynamic feature, like use it for your web browsing or IM.</description>
		<content:encoded><![CDATA[<p>well, I believe the other dynamic forwarding feature is more useful. ssh -D 8080 @, you literally set up a SOCKS5 proxy at port 8080 one your local computer, which then transfers data in the secure channel to your remote host, then to the entire world. You can then do a lot of things with this dynamic feature, like use it for your web browsing or IM.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: cdreyer</title>
		<link>http://www.linux-mag.com/id/5104/#comment-851</link>
		<pubDate>Sat, 16 Feb 2008 06:21:32 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/5104/#comment-851</guid>
					<description>Thanks for the clear and concise explanation for accessing hosts other than the ssh server on a subnet. As a fed up m$ admin and linux newcomer, it is refreshing to participate in the open community.</description>
		<content:encoded><![CDATA[<p>Thanks for the clear and concise explanation for accessing hosts other than the ssh server on a subnet. As a fed up m$ admin and linux newcomer, it is refreshing to participate in the open community.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ongs_1999</title>
		<link>http://www.linux-mag.com/id/5104/#comment-850</link>
		<pubDate>Fri, 15 Feb 2008 23:24:55 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/5104/#comment-850</guid>
					<description>All instructions in this article is only good if your the remote machine is not behind the firewall. If the remote machine is behind the firewall, then you are at the mercy of the network administrator whether he (or she) allows you to open the particular port at the firewall so your SSH process can listen to the login request. Otherwise, the instructions in this article will not work.</description>
		<content:encoded><![CDATA[<p>All instructions in this article is only good if your the remote machine is not behind the firewall. If the remote machine is behind the firewall, then you are at the mercy of the network administrator whether he (or she) allows you to open the particular port at the firewall so your SSH process can listen to the login request. Otherwise, the instructions in this article will not work.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Corne Beerse</title>
		<link>http://www.linux-mag.com/id/5104/#comment-845</link>
		<pubDate>Fri, 15 Feb 2008 10:37:21 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/5104/#comment-845</guid>
					<description>If you ssh from unix to unix, there is a dedicated port forwarding for the X11 (windowing) communication. Hence, if you want the windows from the other machine on your local desktop, just peek for the X11 forwarding and use that, donnot re-invent the wheel by forwarding port 6000 manually.</description>
		<content:encoded><![CDATA[<p>If you ssh from unix to unix, there is a dedicated port forwarding for the X11 (windowing) communication. Hence, if you want the windows from the other machine on your local desktop, just peek for the X11 forwarding and use that, donnot re-invent the wheel by forwarding port 6000 manually.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: john dumont</title>
		<link>http://www.linux-mag.com/id/5104/#comment-841</link>
		<pubDate>Fri, 15 Feb 2008 03:12:33 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/5104/#comment-841</guid>
					<description>my crappy isp does not have secure email or even secure webmail.  I've been succumbed to forwarding a copy to a gmail account and access it from there.
this is awesome.</description>
		<content:encoded><![CDATA[<p>my crappy isp does not have secure email or even secure webmail.  I&#8217;ve been succumbed to forwarding a copy to a gmail account and access it from there.<br />
this is awesome.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
