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

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

<channel>
<title>IPv6 forum - dslreports.com community</title>
<link>http://www.dslreports.com/forum/ipv6</link>
<description>IPv6 forum current topics</description>
<language>en</language>
<copyright>Copyright 2007, dslreports.com</copyright>
<pubDate>Sun, 08 Nov 2009 20:10:35 EDT</pubDate>
<lastBuildDate>Sun, 08 Nov 2009 20:10:35 EDT</lastBuildDate>

<image>
<title>dslreports.com</title>
<url>http://i.dslr.net/bbrdisc1.gif</url>
<link>http://www.dslreports.com</link>
<width>19</width>
<height>18</height>
<description>bbr disc</description>
</image>

<item>
<title>The NEW &#x22;Where does your 6to4 relay address go?&#x22; thread!</title>
<link>http://www.dslreports.com/forum/remark,23150253</link>
<description><![CDATA[A few years ago every server/internet connection I had (CA, TX, PA, and VA) all went to the same relay.  It  would seem there have been quite a few  more put in since then  :D  Here we go!

LA CoLo:
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets&#012; 1  juniperm160-02.lax01.calpop.com (64.27.16.17)  1.248 ms   1.153 ms   0.458 ms&#012; 2  unknown.calpop.com (206.125.44.254)  1.128 ms   0.646 ms   1.074 ms&#012; 3  * * te7-4.ccr01.lax04.atlas.cogentco.com (38.104.83.209)  1.389 ms&#012; 4  te4-3.ccr02.lax01.atlas.cogentco.com (154.54.6.241)  0.754 ms te7-3.ccr01.lax01.atlas.cogentco.com (154.54.24.61)  1.049 ms te4-3.ccr01.lax01.atlas.cogentco.com (154.54.24.69)  1.393 ms&#012; 5  te3-2.ccr02.lax05.atlas.cogentco.com (154.54.6.230)  1.065 ms te3-4.ccr02.lax05.atlas.cogentco.com (154.54.3.10)  0.866 ms te3-2.ccr02.lax05.atlas.cogentco.com (154.54.6.230)  0.829 ms&#012; 6  sl-st31-la-0-0-2-0.sprintlink.net (144.232.9.45)  2.997 ms sl-st31-la-0-4-0-0.sprintlink.net (144.232.24.221)  2.935 ms sl-st31-la-0-0-2-0.sprintlink.net (144.232.9.45)  2.208 ms&#012; 7  sl-crs2-ana-0-10-0-0.sprintlink.net (144.232.24.44)  4.687 ms sl-crs1-ana-0-6-0-0.sprintlink.net (144.232.19.232)  2.879 ms sl-crs2-ana-0-10-0-0.sprintlink.net (144.232.24.44)  4.240 ms&#012; 8  sl-crs1-sj-0-7-0-0.sprintlink.net (144.232.20.223)  11.861 ms sl-crs1-sj-0-8-0-2.sprintlink.net (144.232.18.57)  13.235 ms sl-crs1-sj-0-5-2-0.sprintlink.net (144.232.9.93)  12.243 ms&#012; 9  sl-bb1v6-sj-0-0-0.sprintlink.net (144.232.3.226)  12.143 ms * *&#012;
TX Dedi #1
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets&#012; 1  xx.static.theplanet.com (174.133.168.xxx)  0.437 ms  0.500 ms  0.542 ms&#012; 2  et2-7.ibr01.hstntx1.theplanet.com (207.218.223.9)  0.214 ms  0.257 ms  0.305 ms&#012; 3  et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)  0.197 ms  0.244 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.421 ms&#012; 4  et5-4.ibr03.dllstx3.theplanet.com (70.87.253.49)  6.034 ms  6.065 ms et5-4.ibr04.dllstx3.theplanet.com (70.87.253.53)  5.036 ms&#012; 5  10gigabitethernet3-1.core1.dal1.he.net (206.223.118.37)  5.191 ms te9-1.dsr02.dllstx3.theplanet.com (70.87.253.22)  5.796 ms 10gigabitethernet3-1.core1.dal1.he.net (206.223.118.37)  5.253 ms&#012; 6  et5-2.ibr04.dllstx3.theplanet.com (70.87.253.29)  5.712 ms et3-1.ibr04.dllstx3.theplanet.com (70.87.253.9)  5.660 ms 10gigabitethernet5-2.core1.ash1.he.net (72.52.92.62)  39.572 ms&#012; 7  10gigabitethernet3-1.core1.dal1.he.net (206.223.118.37)  5.718 ms ash.ipv6.he.net (216.218.229.118)  51.819 ms 10gigabitethernet3-1.core1.dal1.he.net (206.223.118.37)  5.778 ms&#012;
TX Dedi #2
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets&#012; 1  xx.static.theplanet.com (70.84.183.xxx)  2.035 ms  2.216 ms  2.436 ms&#012; 2  po102.dsr02.dllstx5.theplanet.com (70.87.254.13)  0.921 ms  0.925 ms  1.139 ms&#012; 3  po52.dsr02.dllstx3.theplanet.com (70.85.127.109)  1.372 ms  1.607 ms  1.841 ms&#012; 4  et5-2.ibr04.dllstx3.theplanet.com (70.87.253.29)  1.329 ms  1.318 ms  1.542 ms&#012; 5  10gigabitethernet3-1.core1.dal1.he.net (206.223.118.37)  1.777 ms  2.007 ms  1.981 ms&#012; 6  10gigabitethernet5-2.core1.ash1.he.net (72.52.92.62)  36.432 ms  35.680 ms  35.665 ms&#012; 7  ash.ipv6.he.net (216.218.229.118)  47.194 ms * *&#012;
VA FiOS connection
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 60 byte packets&#012; 1  192.168.10.1 (192.168.10.1)  0.279 ms  0.239 ms  0.211 ms&#012; 2  L100.RCMDVA-VFTTP-18.verizon-gni.net (98.117.71.1)  3.843 ms  3.871 ms  3.987 ms&#012; 3  G11-1-218.RCMDVA-LCR-02.verizon-gni.net (130.81.129.202)  3.887 ms  3.927 ms  3.970 ms&#012; 4  P15-0-0.RCMDVA-LCR-01.verizon-gni.net (130.81.27.64)  8.533 ms  8.659 ms  8.868 ms&#012; 5  so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net (130.81.28.248)  8.658 ms  8.863 ms  8.905 ms&#012; 6  0.so-6-1-0.XL3.IAD8.ALTER.NET (152.63.36.233)  8.951 ms 0.so-1-2-0.XL3.IAD8.ALTER.NET (152.63.37.117)  9.665 ms 0.so-6-1-0.XL3.IAD8.ALTER.NET (152.63.36.233)  24.679 ms&#012; 7  0.xe-10-0-0.BR1.IAD8.ALTER.NET (152.63.41.149)  9.642 ms  9.666 ms  9.676 ms&#012; 8  sl-st30-ash-0-3-0-0.sprintlink.net (144.232.8.209)  9.726 ms  12.173 ms  12.079 ms&#012; 9  sl-crs1-dc-0-13-0-0.sprintlink.net (144.232.25.12)  12.191 ms sl-crs1-dc-0-1-0-0.sprintlink.net (144.232.19.229)  12.308 ms  12.498 ms&#012;10  sl-crs1-rly-0-13-5-0.sprintlink.net (144.232.19.212)  12.392 ms  12.288 ms sl-crs1-rly-0-9-0-0.sprintlink.net (144.232.20.13)  12.481 ms&#012;11  sl-crs1-rly-0-1-5-0.sprintlink.net (144.232.20.15)  14.346 ms sl-bb1v6-rly-0-0-0.sprintlink.net (144.232.2.55)  12.038 ms sl-crs1-rly-0-1-5-0.sprintlink.net (144.232.20.15)  14.679 ms&#012;
PA Comcast connection
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets&#012; 1  73.154.67.1 (73.154.67.1)  11.930 ms  11.893 ms  11.823 ms&#012; 2  68.85.76.41 (68.85.76.41)  11.756 ms  11.738 ms  11.713 ms&#012; 3  te-9-1-ur01.elizabethtwn.pa.panjde.comcast.net (68.86.209.10)  11.690 ms  13.884 ms  13.899 ms&#012; 4  te-9-1-ur01.lowerswatera.pa.panjde.comcast.net (68.86.209.13)  13.859 ms  13.853 ms  13.828 ms&#012; 5  68.85.158.129 (68.85.158.129)  13.806 ms  13.781 ms  13.754 ms&#012; 6  68.85.158.190 (68.85.158.190)  17.644 ms  12.094 ms  11.347 ms&#012; 7  68.85.159.217 (68.85.159.217)  17.316 ms  17.304 ms  17.265 ms&#012; 8  be-40-crs01.401nbroadst.pa.panjde.comcast.net (68.86.208.33)  17.874 ms  17.885 ms  17.848 ms&#012; 9  pos-1-9-0-0-cr01.mclean.va.ibone.comcast.net (68.86.90.13)  21.644 ms  21.669 ms  21.623 ms&#012;10  ash1-core-2.gigabiteth13-1.swip.net (130.244.200.241)  21.593 ms  21.575 ms  21.645 ms&#012;11  cbv-core-3.pos0-4-3-0.swip.net (130.244.207.205)  102.760 ms  102.765 ms  102.733 ms&#012;12  cbv-core-2.tengigabiteth2-2.swip.net (130.244.52.229)  109.303 ms  102.077 ms  97.794 ms&#012;
/mackey
]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23150253</guid>
<pubDate>2009-10-08 07:55:32</pubDate>
</item>

<item>
<title>IPv6 Traceroute Server</title>
<link>http://www.dslreports.com/forum/remark,23243987</link>
<description><![CDATA[IPv4/IPv6 Traceroute Server
http://4or6.com

Also has ping, dig/nslookup, and whois.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23243987</guid>
<pubDate>2009-10-26 15:35:54</pubDate>
</item>

<item>
<title>multiple ipv6 addresses on one interface</title>
<link>http://www.dslreports.com/forum/remark,23220666</link>
<description><![CDATA[As oppose to ipv4, it seems that a single physical (or virtual) interface can have multiple ipv6 addresses assigned to it. Since we are multi-homed in a way that we have an internal link to our remote sites and we have an "ISP" link to the world, I am wondering how this thing will work. In other words, how the the router or host will know which ipv6 address source to use when sending packets to destination.
In my case let's say I have an interface with 3 ipv6 addresses assigned to it, one link local and two global unicast. My machine(the source) want to send packets to a destination that is not on the same subnet of any of my ipv6 configured addresses. So first hop is the router which will forward the packets according to its routing table. Now the packets will certainly find their way towards destination via whatever route is configured but what about the return packets? . Receiving data on a different link than the sending link will not be allowed on the firewall. 

How do I get control of which ipv6 address I use as a source when I send packets?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,23220666</guid>
<pubDate>2009-10-21 18:38:11</pubDate>
</item>

</channel>
</rss>
