<story><title>Migrating From AWS to FB</title><url>http://instagram-engineering.tumblr.com/post/89992572022/migrating-aws-fb</url></story><parent_chain><item><author>sliverstorm</author><text>I kind of like having standard private subnets. My router is always 192.168.1.1, or sometimes 10.0.1.1, and so is my friend&amp;#x27;s, my parent&amp;#x27;s, and my grandparent&amp;#x27;s.</text></item><item><author>rdl</author><text>Right, but if everyone used IPv6 there would be no need to use non-routeable private IPs for anything, you could just use non-conflicting IPv6 addresses and not route them.</text></item><item><author>cheald</author><text>I think it has more to do with the fact that there are a standard series of private IP blocks.</text></item><item><author>agwa</author><text>&amp;gt; The main blocker to this easy migration was that Facebook’s private IP space conflicts with that of EC2&lt;p&gt;IPv6 adoption could not happen soon enough.</text></item></parent_chain><comment><author>jon-wood</author><text>After spending some time as a contractor doing systems work for a few companies I&amp;#x27;ve stopped ever assigning an internal network to 192.168.0.0, 192.168.1.0, or 10.0.0.0.&lt;p&gt;The number of times I found myself attempting to VPN into a clients network, only to find it conflicted either with my home network, or whatever coffee shop I was sitting in, was ridiculous. Depending how many hosts you need to run on your network there are huge numbers of possible subnets you could use for an internal network - do yourself a favour and keep off the ones set up be default on every router sold.</text></comment>
<story><title>Migrating From AWS to FB</title><url>http://instagram-engineering.tumblr.com/post/89992572022/migrating-aws-fb</url></story><parent_chain><item><author>sliverstorm</author><text>I kind of like having standard private subnets. My router is always 192.168.1.1, or sometimes 10.0.1.1, and so is my friend&amp;#x27;s, my parent&amp;#x27;s, and my grandparent&amp;#x27;s.</text></item><item><author>rdl</author><text>Right, but if everyone used IPv6 there would be no need to use non-routeable private IPs for anything, you could just use non-conflicting IPv6 addresses and not route them.</text></item><item><author>cheald</author><text>I think it has more to do with the fact that there are a standard series of private IP blocks.</text></item><item><author>agwa</author><text>&amp;gt; The main blocker to this easy migration was that Facebook’s private IP space conflicts with that of EC2&lt;p&gt;IPv6 adoption could not happen soon enough.</text></item></parent_chain><comment><author>EvanAnderson</author><text>It creates a lot of pain when you need to connect these networks to each other, though. Admittedly, that&amp;#x27;s probably not a problem for parents, friends, etc.&lt;p&gt;At my Old Job I demanded we keep a &amp;quot;registry&amp;quot; of the RFC1918 address space we allocated to Customers. We never allocated Customers in overlapping address spaces. It made VPN connectivity to Customer A while on-site with Customer B much easier. It also helped out in one case where one Customer acquired another.</text></comment>