With ChaosVPN we've been doing both ipv6 and ipv4. What I have recently seen as a problem at home was choosing private ipv4 allocations for my openstack testing conflicting with allocated chaosvpn space.<br><br>ipv6 would definitelty have been better at this.<br>
<br>however in a mesh / p2p environment you are going to want to be pushing data direct between nodes at time. which will require a vpn... otherwise some folks will end up stuck in ipv6 tunnels.<br><br>-matt<br><br><div class="gmail_quote">
On Thu, Feb 17, 2011 at 10:24 AM, Samuel Gyger <span dir="ltr"><<a href="mailto:samuel@gyger.at">samuel@gyger.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thu, Feb 17, 2011 at 16:29, James Vasile <<a href="mailto:james@hackervisions.org">james@hackervisions.org</a>> wrote:<br>
> So if we are starting at the beginning, we need a device that can<br>
> replace people's routers and then we can layer on the freedom bits.<br>
<br>
</div>As we talk about router, I would suppose don't build on IPv4 anymore.<br>
We should build on the future, should use the possibilities that we<br>
get with IPv6, removing all the problems with NATs etc. Which also<br>
redefines the thing a router should do here.<br>
<font color="#888888"><br>
Samuel<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Freedombox-discuss mailing list<br>
<a href="mailto:Freedombox-discuss@lists.alioth.debian.org">Freedombox-discuss@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss</a><br>
</div></div></blockquote></div><br>