<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Netsh on sigtar.com</title>
		<link>https://sigtar.com/tags/netsh/</link>
		<description>Recent content in Netsh on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Oct 2012 00:00:00 +1300</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/netsh/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Using netsh to create a transparent proxy</title>
				<link>https://sigtar.com/2012/10/16/using-netsh-to-create-a-transparent-proxy/</link>
				<pubDate>Tue, 16 Oct 2012 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2012/10/16/using-netsh-to-create-a-transparent-proxy/</guid>
				<description>&lt;p&gt;There are some good windows web proxies about. The only problem with them is they sometimes dont natively act as a transparent proxy. i.e. typically you&amp;rsquo;ll need to set your client machines to a specific IP and port.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve used squid historically when setting up transparent proxies (mainly since it actually has a transparent mode) and this has worked well. Recently i thought i&amp;rsquo;d have a go at some of the windows solutions to see how they pan out.&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>
	</channel>
</rss>
