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

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

<channel>
<title>Re: IPv6: 6to4 anycast routing through telia.net, Sweden? in AT&#x26;T Midwest</title>
<link>http://www.dslreports.com/forum/r20453749</link>
<description></description>
<language>en</language>
<pubDate>Thu, 08 Jan 2009 04:23:03 EDT</pubDate>
<lastBuildDate>Thu, 08 Jan 2009 04:23:03 EDT</lastBuildDate>

<item>
<title>Re: IPv6: 6to4 anycast routing through telia.net, Sweden?</title>
<link>http://www.dslreports.com/forum/remark,20459571</link>
<description><![CDATA[<A HREF="/useremail/u/1364148"><b>jeixav</b></A> : I vaguely remember that the general feeling in the IPv6 community is that, at least at this point in time, using a public 6to4 relay is suboptimal. For example see the last comment in this thread: &raquo;<A HREF="http://noc.sixxs.net/forum/?msg=apps-540625" >noc.sixxs.net/forum/?msg=apps-540625</A>. Jeroen Massar is one of SixXS's founder's so he must have extensive experience with IPv6 and if he says not rely on 6to4 relays for good IPv6 connectivity, he most probably has sound reasons for saying this.<br><br>If you're in Chicago, both tunnelbroker.net and SixXS have PoPs there (SixXS's PoP is provided by your.org, the ISP that shows up in your traceroute with Comcast.) I've successfully used both.<br><br>I apologize if this information is of no use to you, however, I wanted to point alternatives to using a public 6to4 relay in case it's something you haven't considered.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20459571</guid>
<pubDate>Fri, 09 May 2008 22:39:20 EDT</pubDate>
</item>

<item>
<title>Re: IPv6: 6to4 anycast routing through telia.net, Sweden?</title>
<link>http://www.dslreports.com/forum/remark,20453749</link>
<description><![CDATA[<A HREF="/useremail/u/891119"><b>Shadow01</b></A> : Although the info is good to know for members of the open forum, we are not in a position to alter the routing as the OP is requesting.  If this is outside the per view of Direct, then they need to push the issue up the chain.  ;)<br><small>--<br>R.I.P. Moby 1964 - 2007</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20453749</guid>
<pubDate>Thu, 08 May 2008 20:31:53 EDT</pubDate>
</item>

<item>
<title>Re: IPv6: 6to4 anycast routing through telia.net, Sweden?</title>
<link>http://www.dslreports.com/forum/remark,20453305</link>
<description><![CDATA[<A HREF="/useremail/u/296798"><b>Dennis</b></A> : <div class="bquote"><small>said by  Shadow01 <A HREF="/useremail/u/891119"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>If you wanted to rattle a cage, you should have posted in Direct... You will get more milage there.  ;)<br> </div>I actually recommended against it....I thought that this information might come across better eyes in a public forum.<br><small>--<br><A HREF="http://www.dennisjudd.com">My Blog. Because I desperately need the acknowledgement of others.</a><br><br><A HREF="http://www.dennisjudd.com/connor">Meet my son, Connor.</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20453305</guid>
<pubDate>Thu, 08 May 2008 18:37:18 EDT</pubDate>
</item>

<item>
<title>Re: IPv6: 6to4 anycast routing through telia.net, Sweden?</title>
<link>http://www.dslreports.com/forum/remark,20453166</link>
<description><![CDATA[<A HREF="/useremail/u/891119"><b>Shadow01</b></A> : If you wanted to rattle a cage, you should have posted in Direct... You will get more milage there.  ;)<br><small>--<br>R.I.P. Moby 1964 - 2007</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20453166</guid>
<pubDate>Thu, 08 May 2008 18:09:39 EDT</pubDate>
</item>

<item>
<title>IPv6: 6to4 anycast routing through telia.net, Sweden?</title>
<link>http://www.dslreports.com/forum/remark,20452814</link>
<description><![CDATA[<A HREF="/useremail/u/749583"><b>justbits</b></A> : I don't suppose an AT+T employee could rattle some cages and get someone to clean up the routes for the IPV6 anycast BGP routes that AT+T accepts/uses?<br>Right now, it's routing all 6to4 IPv6 traffic through Telia.net (Sweden). It's been like this since mid-February.<br>More info on the 192.88.99.1 6to4 anycast relay address can be found here: &raquo;<A HREF="http://tools.ietf.org/html/rfc3068" >tools.ietf.org/html/rfc3068</A><br><textarea name="code" class="text" cols=50 rows=10>$ traceroute 192.88.99.1&#012;traceroute to 192.88.99.1 (192.88.99.1), 64 hops max, 40 byte packets&#012;2 adsl-68-75-183-254.dsl.emhril.ameritech.net (68.75.183.254) 12.258 ms 9.552 ms 9.048 ms&#012;3 dist2-vlan60.emhril.ameritech.net (68.22.72.131) 9.349 ms 9.374 ms 9.794 ms&#012;4 bb2-g9-0.emhril.sbcglobal.net (151.164.94.164) 10.526 ms 9.671 ms 10.331 ms&#012;5 151.164.95.166 (151.164.95.166) 10.296 ms 10.079 ms 10.309 ms&#012;6 asn1299-telia.eqchil.sbcglobal.net (151.164.250.150) 10.060 ms 10.330 ms 10.610 ms&#012;7 nyk-bb1-pos0-3-0.telia.net (213.248.80.154) 31.445 ms nyk-bb1-link.telia.net (80.91.248.194) 32.190 ms nyk-bb2-link.telia.net (80.91.248.198) 31.852 ms&#012;8 kbn-bb1-link.telia.net (80.91.254.88) 117.737 ms kbn-bb2-link.telia.net (213.248.82.102) 117.955 ms 117.020 ms&#012;9 s-bb1-link.telia.net (80.91.248.46) 127.834 ms s-bb2-link.telia.net (80.91.248.50) 127.474 ms s-bb1-link.telia.net (80.91.248.46) 128.028 ms&#012;10 s-b1-link.telia.net (80.91.254.117) 133.182 ms s-b1-link.telia.net (80.91.252.125) 359.254 ms 151.831 ms&#012;11 *^C&#012;</textarea><!--end code block-->From this thread, you can see that there are "local" BGP routes that would be more appropriate.<br>&raquo;<A HREF="/forum/r17914554-Where-does-your-6to4-relay-address-19288991-go">Where does your 6to4 relay address (192.88.99.1) go?</A><br><br>From a Comcast Business line, I get better performance because they're using the route for a local 6to4 relay:<br><textarea name="code" class="text" cols=50 rows=10>$ traceroute 192.88.99.1&#012;traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets&#012;1 * * *&#012;2 ge-2-8-ur01.elmhurst.il.chicago.comcast.net (68.86.115.225) 9.669 ms 15.402 ms 10.216 ms&#012;3 te-8-3-ur02.elmhurst.il.chicago.comcast.net (68.87.230.86) 8.864 ms 10.341 ms 10.168 ms&#012;4 te-3-1-ar01.chartford.ct.hartford.comcast.net (68.86.90.58) 15.345 ms 17.538 ms 10.746 ms&#012;5 pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.57) 11.816 ms 11.302 ms 11.891 ms&#012;6 68.86.89.58 (68.86.89.58) 12.458 ms 10.411 ms 11.359 ms&#012;7 your.org.ge2-5.br02.chc01.pccwbtn.net (63.218.5.38) 12.295 ms 14.564 ms 11.484 ms&#012;8 for.info.about.this.relay.see-.www.6to4.your.org (216.14.98.42) 13.19 ms 17.202 ms 18.324 ms&#012;9 192.88.99.1 (192.88.99.1) 11.904 ms 11.706 ms 14.765 ms&#012;</textarea><!--end code block--><br>Thank you!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20452814</guid>
<pubDate>Thu, 08 May 2008 17:04:48 EDT</pubDate>
</item>

</channel>
</rss>
