<?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>Somewhere out there! &#187; routing</title>
	<atom:link href="http://stateless.geek.nz/tag/routing/feed/" rel="self" type="application/rss+xml" />
	<link>http://stateless.geek.nz</link>
	<description></description>
	<lastBuildDate>Sun, 18 Oct 2009 11:03:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Source routing for a VPN node in Linux</title>
		<link>http://stateless.geek.nz/2008/06/01/source-routing-for-a-vpn-node-in-linux/</link>
		<comments>http://stateless.geek.nz/2008/06/01/source-routing-for-a-vpn-node-in-linux/#comments</comments>
		<pubDate>Sat, 31 May 2008 22:08:00 +0000</pubDate>
		<dc:creator>Nicholas Lee</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[routing]]></category>

		<guid isPermaLink="false">http://stateless.geek.nz/?p=558</guid>
		<description><![CDATA[Occansion in Linux when running a VPN you want to generate traffic from the VPN server node. By default Linux uses the IP of the interface used to route a package. The might often complicated the routing tables required at client networks.
A solution to fix this issue is to use Linux source/policy routing. For example, [...]]]></description>
			<content:encoded><![CDATA[<p>Occansion in Linux when running a VPN you want to generate traffic from the VPN server node. By default Linux uses the IP of the interface used to route a package. The might often complicated the routing tables required at client networks.</p>
<p>A solution to fix this issue is to use Linux source/policy <a href="http://linux-ip.net/gl/ip-cref/node77.html">routing</a>. For example, for node with IP 192.168.10.1 and VPN server IP 172.29.148.1, route <strong>to</strong> subnet 192.168.9.0/24 out 172.29.148.1 <strong>via</strong> 172.29.148.2 with <strong>src (source)</strong> IP 192.168.10.1:</p>
<p><code><br />
sudo ip route add to 192.168.9.0/24 src 192.168.10.1 via 172.29.148.2<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://stateless.geek.nz/2008/06/01/source-routing-for-a-vpn-node-in-linux/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
