<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Reallywow &#187; proxy</title>
	<atom:link href="http://blog.reallywow.com/archives/tag/proxy/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.reallywow.com</link>
	<description>Really? Wow... That's Reallywow</description>
	<lastBuildDate>Thu, 27 May 2010 15:02:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>IRC Blocked? Create an SSH tunnel with PuTTY</title>
		<link>http://blog.reallywow.com/archives/83</link>
		<comments>http://blog.reallywow.com/archives/83#comments</comments>
		<pubDate>Fri, 12 Jun 2009 16:19:06 +0000</pubDate>
		<dc:creator>lbjay</dc:creator>
				<category><![CDATA[hacks]]></category>
		<category><![CDATA[proxy]]></category>
		<category><![CDATA[putty]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://blog.reallywow.com/?p=83</guid>
		<description><![CDATA[Can&#8217;t get to IRC because port 6667 is blocked on your local network? Here are some instructions for how to create a SSH tunnel using  PuTTY, and then connect to freenode (or any other IRC server) with Pidgin using the tunnel as a SOCKS5 proxy. You can most likely s/Pidgin/your IRC client of choice/, but [...]]]></description>
			<content:encoded><![CDATA[<abbr class="unapi-id" title="http://blog.reallywow.com/?p=83"><!-- &nbsp; --></abbr>
<p>Can&#8217;t get to IRC because port 6667 is blocked on your local network? Here are some instructions for how to create a SSH tunnel using  <a href="http://www.putty.org/">PuTTY</a>, and then connect to freenode (or any other IRC server) with <a href="http://www.pidgin.im/">Pidgin</a> using the tunnel as a SOCKS5 proxy. You can most likely <em>s/Pidgin/your IRC client of choice/</em>, but the screenshots below will show the Pidgin config dialogs. These instructions also assume that SSH, port 22, is not also blocked. Woe be to you if that is the case.</p>
<p>My original source for how to do this was <a href="http://everythinghurts.com/ssh-tunnelling/">this post</a>, which describes the same trick but for FireFox.</p>
<p><strong>Step 1</strong>: create a new PuTTY session configuration. In this case I using the login <strong>me@ssh.example.com</strong> and calling the session <strong>irc-7777</strong>. I usually name the session based on the local port number I&#8217;m going to forward.</p>
<div id="attachment_93" class="wp-caption aligncenter" style="width: 466px"><img class="size-full wp-image-93" title="putty1" src="http://blog.reallywow.com/wp-content/uploads/2009/06/putty11.png" alt="create and save a new PuTTY session " width="456" height="435" /><p class="wp-caption-text">create and save a new PuTTY session </p></div>
<p><strong>Step 2</strong>: go to the <strong>Connection -&gt; SSH -&gt; Tunnels</strong> node of the session config. In the Source port field enter &#8220;7777&#8243; (or some other port number). In the radio button section below that select <strong>Dynamic</strong> and <strong>Auto</strong>. Click the <strong>Add</strong> button. You should see &#8220;D7777&#8243; appear in the list of forwarded ports.</p>
<div id="attachment_94" class="wp-caption aligncenter" style="width: 466px"><img class="size-full wp-image-94" title="putty2" src="http://blog.reallywow.com/wp-content/uploads/2009/06/putty21.png" alt="Configure the ssh tunnel " width="456" height="435" /><p class="wp-caption-text">Configure the ssh tunnel </p></div>
<div id="attachment_95" class="wp-caption aligncenter" style="width: 466px"><img class="size-full wp-image-95" title="putty3" src="http://blog.reallywow.com/wp-content/uploads/2009/06/putty31.png" alt="Tunnel D7777 appears in the list" width="456" height="435" /><p class="wp-caption-text">Tunnel D7777 appears in the list</p></div>
<p><strong>Step 3</strong>: go back to the man session config node and save the session again. Then open the PuTTY session by clicking the <strong>Open</strong> button. A normal looking PuTTY terminal window should open. This session is your tunnel so you should probably leave it be. i.e., don&#8217;t use it for doing stuff in the shell and as a tunnel (although I don&#8217;t really know what consequences that would lead to). If the fact that this tunnel takes up space in your TaskBar (it does me) check out <a href="http://haanstra.eu/putty/">PuTTY-Tray</a>.</p>
<div id="attachment_97" class="wp-caption aligncenter" style="width: 310px"><img class="size-medium wp-image-97" title="putty4" src="http://blog.reallywow.com/wp-content/uploads/2009/06/putty4-300x150.png" alt="You've probably never seen one of these before" width="300" height="150" /><p class="wp-caption-text">You&#39;ve probably never seen one of these before</p></div>
<p><strong>Step 4</strong>: Configure your Pidgin IRC account to use the tunnel as a SOCKS5 proxy. Go to Accounts -&gt; Manage Accounts. Highlight your IRC protocol account and click Modify (or create one by clicking Add). Go to the Advanced tab of the config dialog. In the Proxy Options section select SOCKS5 as the proxy type, enter &#8220;localhost&#8221; as the Host and &#8220;7777&#8243; (or whatever port you used) as the Port.</p>
<div id="attachment_96" class="wp-caption aligncenter" style="width: 314px"><img class="size-full wp-image-96" title="pidgin" src="http://blog.reallywow.com/wp-content/uploads/2009/06/pidgin1.png" alt="Specify your local tunnel as the SOCKS5 proxy" width="304" height="520" /><p class="wp-caption-text">Specify your local tunnel as the SOCKS5 proxy</p></div>
<p>Save and that&#8217;s it. You should be able to connect to IRC server through Pidgin.</p>
<p>On a *nix machine (or using Cygwin, I suppose) this is, of course, much simpler. You can replace the PuTTY steps with a single ssh command: <em>ssh -D localhost:7777 me@ssh.example.com</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.reallywow.com/archives/83/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
