<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Tunnel on sigtar.com</title>
		<link>https://sigtar.com/tags/tunnel/</link>
		<description>Recent content in Tunnel on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Mon, 27 Jun 2022 00:00:00 +1200</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/tunnel/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Using a CDN at home for free!</title>
				<link>https://sigtar.com/2022/06/27/using-cloudflare-at-home/</link>
				<pubDate>Mon, 27 Jun 2022 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2022/06/27/using-cloudflare-at-home/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://blog-cloudflare-com-assets.storage.googleapis.com/2019/07/cf-logo-social-media.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Cloudflare are nice enough to provide a free tier to their CDN service which is perfect for those of us that still host websites at home. The free teir provides some basic benefits - DDOS protection and caching. Check out the details here - &lt;a href=&#34;https://www.cloudflare.com/plans/#overview&#34;&gt;https://www.cloudflare.com/plans/#overview&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;If you utilize their tunneling solution, you&amp;rsquo;ll also be able to host websites behind a dynamic IP. You&amp;rsquo;ll no longer need a static IP. This means the traffic goes like so;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Windows - Port forwarding</title>
				<link>https://sigtar.com/2009/02/19/windows-port-fowarding/</link>
				<pubDate>Thu, 19 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/19/windows-port-fowarding/</guid>
				<description>&lt;p&gt;Just wanted to note here that there is a tool for windows to &amp;lsquo;port forward&amp;rsquo; Its a command MS ships that enables IPv6 to work on IPv4, but can be used as a port redirector&amp;hellip;. so as long as you have IPv6 support on your box, you can do this.&lt;/p&gt;&#xA;&lt;p&gt;syntax as follows;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;netsh interface portproxy add v4tov4 listenport=443 connectaddress=targetmachine connectport=3389&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;so the machine above listens on 443 and redirects traffic to 3389 on targetmachine.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Corporate Firewall - SSH and port 443 goodness</title>
				<link>https://sigtar.com/2009/02/08/corporate-firewall-ssh-and-port-443-goodness/</link>
				<pubDate>Sun, 08 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/08/corporate-firewall-ssh-and-port-443-goodness/</guid>
				<description>&lt;p&gt;Things you&amp;rsquo;ll need; (basic instructions) SSH - either Linux or Open SSH for windows (set this up first and ensure its working!). I have only used Linux, so i do not know the details of setting up a Open SSH box on windows (good luck).&lt;/p&gt;&#xA;&lt;p&gt;Router with pinhole or port forwarding abilities. &amp;ndash; forward your external 443 port to internal 22 on your SSH box&lt;/p&gt;&#xA;&lt;p&gt;Putty.exe - use this to test your SSH connection locally (you should be able to connect on port 22 locally or 443 externally)&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
