<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;tunneling to the ipv6 cloud&#x27; in forum &#x27;IPv6&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/tunneling-to-the-ipv6-cloud-22968446</link>
<description></description>
<language>en</language>
<pubDate>Sat, 11 Feb 2012 06:54:47 EDT</pubDate>
<lastBuildDate>Sat, 11 Feb 2012 06:54:47 EDT</lastBuildDate>

<item>
<title>Re: tunneling to the ipv6 cloud</title>
<link>http://www.dslreports.com/forum/Re-tunneling-to-the-ipv6-cloud-22980341</link>
<description><![CDATA[AVonGauss posted : Essentially, yes, what you are doing is creating an IPv6 tunnel to Hurricane Electric who has many different IPv6 backbone connections.  Some routers can directly create the tunnel or you can always use an existing server to perform this functionality.  The advantage and difference of a HE BGP tunnel is you can use BGP to announce your own prefix availability thus allowing them to be globally accessible.<br><br>With a BGP tunnel, after the tunnel is activated I believe the first step is to set up a transit tunnel session to Hurricane Electric for IPv6.  I believe you could use any regular HE tunnel HOWTO or instructions geared towards your target device.  Once the transit tunnel is established, then you would need to configure BGP to properly announce the prefixes you wish.<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#FFFFFF nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/22980341?c=1466130&ret=L2ZvcnVtL3IyMjk2ODQ0Ni54bWw%3D"><IMG class="apic" BORDER=0 TITLE="296364 bytes" WIDTH=600 HEIGHT=452 SRC="/r0/download/1466130.thumb600~bd4741c01b1a0986ac777cb63c356f39/BGP.png/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-tunneling-to-the-ipv6-cloud-22980341</guid>
<pubDate>Sat, 05 Sep 2009 22:28:03 EDT</pubDate>
</item>

<item>
<title>Re: tunneling to the ipv6 cloud</title>
<link>http://www.dslreports.com/forum/Re-tunneling-to-the-ipv6-cloud-22979966</link>
<description><![CDATA[fantomas posted : <div class="bquote"><small>said by <a href="/profile/1499612" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1499612');">AVonGauss</a>:</small><br><br>If I'm understanding right, you have a public ASN allocation (i.e. 2001::/48) but your ISP does not yet provide direct IPv6 transit? <br> </div>Yes you understand it right. <br>But I am still wondering how a tunnel broker works. I am guessing that when we sign up with hurricane electric or other, we give them the list of IPv6 interface that we use and then they interconnect our network to the IPv6 cloud? What is the necessary configuration on our side, just the IPv6 default gateway and a tunnel interface?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-tunneling-to-the-ipv6-cloud-22979966</guid>
<pubDate>Sat, 05 Sep 2009 20:23:32 EDT</pubDate>
</item>

<item>
<title>Re: tunneling to the ipv6 cloud</title>
<link>http://www.dslreports.com/forum/Re-tunneling-to-the-ipv6-cloud-22976757</link>
<description><![CDATA[AVonGauss posted : If I'm understanding right, you have a public ASN allocation (i.e. 2001::/48) but your ISP does not yet provide direct IPv6 transit?  I'm not sure that a 6to4 connection would work, but I'm not a 100% sure about that.  If you haven't already, what I would consider doing is setting up a BGP tunnel with a tunnel broker such as Hurricane Electric.  That would allow you to use your ASN publicly via the tunnel normally until your ISP provides direct IPv6 transit.<br><br>Hurricane Electric's Tunnel Broker:<br>&raquo;<A HREF="http://www.tunnelbroker.net" >www.tunnelbroker.net</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-tunneling-to-the-ipv6-cloud-22976757</guid>
<pubDate>Fri, 04 Sep 2009 22:51:27 EDT</pubDate>
</item>

<item>
<title>tunneling to the ipv6 cloud</title>
<link>http://www.dslreports.com/forum/tunneling-to-the-ipv6-cloud-22968446</link>
<description><![CDATA[fantomas posted : Hi,<br>We have native IPv6 deployed on our entire internal network and now I would like to connect our network to the ipv6 cloud.<br>We are using several global ipv6 interfaces (subnets) and everything is routed internally. Problem is our internet providers who don't seem to be interconnecting IPv6 networks anytime soon. So we are on an island. I am trying to figure out the different tunneling options and I feel like we have to move toward a 6to4 tunnel. But here, I have hard time understanding the technical details of it. <br>We don't have any remote site that we could test ipv6 connectivity with but we would definitely like to connect to the rest of the ipv6 cloud. Meaning that there is only one endpoint that I can configure, ours.<br><br>Please correct me if I'm wrong but it looks like I have to configure my router to default route to a "public" ipv6 relay router that would be the boundary between the ipv4 and the ipv6 cloud. Assuming that the clients would not be using their global ipv6 address but instead use a 6t4 address. then I'm all set, right?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/tunneling-to-the-ipv6-cloud-22968446</guid>
<pubDate>Thu, 03 Sep 2009 12:50:06 EDT</pubDate>
</item>

</channel>
</rss>

