<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: OpenSim on OSGrid &#8211; A HOWTO</title>
	<atom:link href="http://www.adamfrisby.com/blog/2009/08/opensim-on-osgrid-a-howto/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamfrisby.com/blog/2009/08/opensim-on-osgrid-a-howto/</link>
	<description>ZOMGWTFHAI</description>
	<lastBuildDate>Tue, 02 Feb 2010 23:36:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Quincie</title>
		<link>http://www.adamfrisby.com/blog/2009/08/opensim-on-osgrid-a-howto/comment-page-1/#comment-8457</link>
		<dc:creator>Quincie</dc:creator>
		<pubDate>Sun, 27 Sep 2009 01:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=399#comment-8457</guid>
		<description>We need more posts like this!</description>
		<content:encoded><![CDATA[<p>We need more posts like this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr B the Master</title>
		<link>http://www.adamfrisby.com/blog/2009/08/opensim-on-osgrid-a-howto/comment-page-1/#comment-8379</link>
		<dc:creator>Dr B the Master</dc:creator>
		<pubDate>Wed, 26 Aug 2009 15:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=399#comment-8379</guid>
		<description>Addendum to my last post.

If running a grid on a home network, using a router that doesn&#039;t support NAT loopback.

Add two other iptables rules, and use ports 8001:8006 and port 80 if using wiredux</description>
		<content:encoded><![CDATA[<p>Addendum to my last post.</p>
<p>If running a grid on a home network, using a router that doesn&#8217;t support NAT loopback.</p>
<p>Add two other iptables rules, and use ports 8001:8006 and port 80 if using wiredux</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr B the Master</title>
		<link>http://www.adamfrisby.com/blog/2009/08/opensim-on-osgrid-a-howto/comment-page-1/#comment-8377</link>
		<dc:creator>Dr B the Master</dc:creator>
		<pubDate>Tue, 25 Aug 2009 07:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=399#comment-8377</guid>
		<description>On the subject of NAT loopback.

It is possible to trick a router into supporting NAT loopback if it&#039;s not supported by the router.

A good knowledge of Linux iptables is required, and the router MUST be running an embedded Linux such as BusyBox.

First access the router via telnet, then at the routers console, use the commands written below.

NOTE.
replace $INET with your internet IP address or hostname without http://
replace $LANIP with your home servers LAN IP address
replace $GATEWAY with your routers IP address.
replace $OPENSIMPORT(S) with the port or port range your regions are using, ei, 9000 for single port or 9000:9050 for a 50 port range

iptables -t nat -I PREROUTING --dst $INET -p tcp --dport $OPENSIMPORT(S) -j DNAT --to-destination $LANIP

repeat above line and replace tcp with udp

iptables -t nat -A POSTROUTING --dst $LANIP -p tcp --dport $OPENSIMPORT(S) -j SNAT --to-source $GATEWAY

repeat and replace tcp with udp

This works on my router, and should work on almost all routers that use embedded Linux, but,,,,depending on the router, the lines may stay when power to the router is interrupted, or you may have to re-write the iptables rules everytime power to the router is interrupted.</description>
		<content:encoded><![CDATA[<p>On the subject of NAT loopback.</p>
<p>It is possible to trick a router into supporting NAT loopback if it&#8217;s not supported by the router.</p>
<p>A good knowledge of Linux iptables is required, and the router MUST be running an embedded Linux such as BusyBox.</p>
<p>First access the router via telnet, then at the routers console, use the commands written below.</p>
<p>NOTE.<br />
replace $INET with your internet IP address or hostname without http://<br />
replace $LANIP with your home servers LAN IP address<br />
replace $GATEWAY with your routers IP address.<br />
replace $OPENSIMPORT(S) with the port or port range your regions are using, ei, 9000 for single port or 9000:9050 for a 50 port range</p>
<p>iptables -t nat -I PREROUTING &#8211;dst $INET -p tcp &#8211;dport $OPENSIMPORT(S) -j DNAT &#8211;to-destination $LANIP</p>
<p>repeat above line and replace tcp with udp</p>
<p>iptables -t nat -A POSTROUTING &#8211;dst $LANIP -p tcp &#8211;dport $OPENSIMPORT(S) -j SNAT &#8211;to-source $GATEWAY</p>
<p>repeat and replace tcp with udp</p>
<p>This works on my router, and should work on almost all routers that use embedded Linux, but,,,,depending on the router, the lines may stay when power to the router is interrupted, or you may have to re-write the iptables rules everytime power to the router is interrupted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim "Omar" Siler</title>
		<link>http://www.adamfrisby.com/blog/2009/08/opensim-on-osgrid-a-howto/comment-page-1/#comment-8360</link>
		<dc:creator>Jim "Omar" Siler</dc:creator>
		<pubDate>Wed, 19 Aug 2009 12:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=399#comment-8360</guid>
		<description>On the subject of NAT loopback, the following is a solution that has worked for several people without loopback routers.  I have not tested it personally as my routers support loopback.

(see http://opensimulator.org/wiki/Network_Settings)

On the system running the viewer, modify the hosts file to add an entry for the external host name of your region server, listing the internal address.  For example, if your external host name is &quot;yadayada.dyndns.org&quot; and the internal address of your region server is 192.168.0.10, you host file line will read &quot;192.168.0.10 yadayada.dyndns.org&quot;.  

On a Linux box the file is /etc/hosts.  On windows it is typically C:\windows\system32\drivers\etc\hosts.

This will override the DNS address for yadayada.dyndns.org on your viewer&#039;s machine, so that when the viewer tries to connect to that host, it will reach its local address.

I any case, it will almost always be cheaper to replace the router with one that does loopback than to go to an external hosting provider, although there are many other advantages to a hosted solution.</description>
		<content:encoded><![CDATA[<p>On the subject of NAT loopback, the following is a solution that has worked for several people without loopback routers.  I have not tested it personally as my routers support loopback.</p>
<p>(see <a href="http://opensimulator.org/wiki/Network_Settings)" rel="nofollow">http://opensimulator.org/wiki/Network_Settings)</a></p>
<p>On the system running the viewer, modify the hosts file to add an entry for the external host name of your region server, listing the internal address.  For example, if your external host name is &#8220;yadayada.dyndns.org&#8221; and the internal address of your region server is 192.168.0.10, you host file line will read &#8220;192.168.0.10 yadayada.dyndns.org&#8221;.  </p>
<p>On a Linux box the file is /etc/hosts.  On windows it is typically C:\windows\system32\drivers\etc\hosts.</p>
<p>This will override the DNS address for yadayada.dyndns.org on your viewer&#8217;s machine, so that when the viewer tries to connect to that host, it will reach its local address.</p>
<p>I any case, it will almost always be cheaper to replace the router with one that does loopback than to go to an external hosting provider, although there are many other advantages to a hosted solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim "Omar" Siler</title>
		<link>http://www.adamfrisby.com/blog/2009/08/opensim-on-osgrid-a-howto/comment-page-1/#comment-8359</link>
		<dc:creator>Jim "Omar" Siler</dc:creator>
		<pubDate>Wed, 19 Aug 2009 12:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=399#comment-8359</guid>
		<description>On the subject of NAT loopback, the following is a solution that has worked for several people without loopback routers.  I have not tested it personally as my routers support loopback.

On the system running the viewer, modify the hosts file to add an entry for the external host name of your region server, listing the internal address.  For example, if your external host name is &quot;yadayada.dyndns.org&quot; and the internal address of your region server is 192.168.0.10, you host file line will read &quot;192.168.0.10 yadayada.dyndns.org&quot;.  

On a Linux box the file is /etc/hosts.  On windows it is typically C:\windows\system32\drivers\etc\hosts.

This will override the DNS address for yadayada.dyndns.org on your viewer&#039;s machine, so that when the viewer tries to connect to that host, it will reach its local address.

I any case, it will almost always be cheaper to replace the router with one that does loopback than to go to an external hosting provider, although there are many other advantages to a hosted solution.</description>
		<content:encoded><![CDATA[<p>On the subject of NAT loopback, the following is a solution that has worked for several people without loopback routers.  I have not tested it personally as my routers support loopback.</p>
<p>On the system running the viewer, modify the hosts file to add an entry for the external host name of your region server, listing the internal address.  For example, if your external host name is &#8220;yadayada.dyndns.org&#8221; and the internal address of your region server is 192.168.0.10, you host file line will read &#8220;192.168.0.10 yadayada.dyndns.org&#8221;.  </p>
<p>On a Linux box the file is /etc/hosts.  On windows it is typically C:\windows\system32\drivers\etc\hosts.</p>
<p>This will override the DNS address for yadayada.dyndns.org on your viewer&#8217;s machine, so that when the viewer tries to connect to that host, it will reach its local address.</p>
<p>I any case, it will almost always be cheaper to replace the router with one that does loopback than to go to an external hosting provider, although there are many other advantages to a hosted solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WhiteStar Magic</title>
		<link>http://www.adamfrisby.com/blog/2009/08/opensim-on-osgrid-a-howto/comment-page-1/#comment-8343</link>
		<dc:creator>WhiteStar Magic</dc:creator>
		<pubDate>Mon, 10 Aug 2009 15:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamfrisby.com/blog/?p=399#comment-8343</guid>
		<description>Please Note for anyone installing OpenSim.

Windows .NET users:
You MUST have .NET Framework 3.51 which is (3.5 SP-1)
http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&amp;displaylang=en
You are better off downloading the FULL PACKAGE of 231 meg.  Bootstrapper has some issues depending on version of Windows.

Linux Users:
MONO Version 2.4.x is required.  2.4.2 is stable and used most often, yu will have to use teh appropriate distro for the flavour of Linux you are using.
http://www.mono-project.com/Main_Page will assist you but there are numerous other sources and versions.</description>
		<content:encoded><![CDATA[<p>Please Note for anyone installing OpenSim.</p>
<p>Windows .NET users:<br />
You MUST have .NET Framework 3.51 which is (3.5 SP-1)<br />
<a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&amp;displaylang=en" rel="nofollow">http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&amp;displaylang=en</a><br />
You are better off downloading the FULL PACKAGE of 231 meg.  Bootstrapper has some issues depending on version of Windows.</p>
<p>Linux Users:<br />
MONO Version 2.4.x is required.  2.4.2 is stable and used most often, yu will have to use teh appropriate distro for the flavour of Linux you are using.<br />
<a href="http://www.mono-project.com/Main_Page" rel="nofollow">http://www.mono-project.com/Main_Page</a> will assist you but there are numerous other sources and versions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
