Topic 'The NEW "Where does your 6to4 relay address go?" thread!' in forum 'IPv6' - dslreports.com

Re: The NEW "Where does your 6to4 relay address go?" thread!

Wed, 27 Jan 2010 01:10:55 EDT

zfin posted : Trace from home. Different ISP.

zfin@homezone:~$ sudo tracert 192.88.99.1traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 60 byte packets1,2: removed for privacy3  csc.ficix2-ge.ficix.fi (193.110.224.14)  19.720 ms  19.852 ms  20.128 ms4  csc0-x0000-helsinki0.funet.fi (193.166.255.153)  20.364 ms  20.681 ms  21.321 ms5  192.88.99.1 (192.88.99.1)  21.452 ms  21.816 ms

Re: The NEW "Where does your 6to4 relay address go?" thread!

Tue, 26 Jan 2010 07:02:17 EDT

zfin posted : From Office.

1,2: Removed for privacy  3    10 ms    10 ms    16 ms  172.16.4.230  4    10 ms    10 ms    16 ms  172.16.3.137  5    11 ms     *        *     suomicom-transit.nebula.fi [217.30.185.66]  6     *        *      194 ms  rtr1-v1348.pas.hel.fi.nblnet.com [83.150.93.98]  7    11 ms    21 ms    11 ms  csc.ficix2-ge.ficix.fi [193.110.224.14]  8    11 ms    13 ms    11 ms  csc0-x0000-helsinki0.funet.fi [193.166.255.153]  9    11 ms    10 ms    11 ms  192.88.99.1

Whoa! Some you you guys got LONG and SLOW route...

Re: The NEW "Where does your 6to4 relay address go?" thread!

Wed, 09 Dec 2009 19:08:34 EDT

ajmas posted : Mine goes from Montreal, Canada to Sweden, if my background checking on swip.net is correct.

traceroute to 192.88.99.1 (192.88.99.1), 64 hops max, 52 byte packets 1  10.0.1.1 (10.0.1.1)  1.068 ms  0.946 ms  0.753 ms 2  bas7-montreal28_lo0_symp.net.bell.ca (64.230.197.166)  7.913 ms  12.263 ms  7.257 ms 3  dis23-montreal02_vlan134.net.bell.ca (64.230.172.225)  6.424 ms  6.447 ms  6.090 ms 4  core4-montreal02_gig12-2.net.bell.ca (64.230.170.137)  6.187 ms  6.510 ms  6.275 ms 5  ncore3-montreal02_pos0-8-0-0_core.net.bell.ca (64.230.168.221)  6.782 ms  170.458 ms  78.262 ms 6  newcore1-newyork83_so1-0-0.net.bell.ca (64.230.187.129)  45.846 ms  13.287 ms  14.438 ms 7  core1-newyork83_pos3-0-0_core.net.bell.ca (64.230.187.82)  27.552 ms  13.024 ms  13.064 ms 8  nyc9-core-2.gigabiteth0-2.swip.net (130.244.200.69)  14.293 ms  170.506 ms  21.690 ms 9  nyc9-core-1.pos9-0.swip.net (130.244.194.206)  13.664 ms  234.319 ms  174.643 ms10  130.244.218.213 (130.244.218.213)  128.088 ms  91.624 ms  92.543 ms11  ams13-core-1.tengigabiteth2-4.swip.net (130.244.52.169)  316.047 ms  313.822 ms

Re: The NEW "Where does your 6to4 relay address go?" thread!

Fri, 13 Nov 2009 16:20:45 EDT

whfsdude posted :

traceroute to 192.88.99.1 (192.88.99.1), 64 hops max, 52 byte packets 1  192.168.123.1 (192.168.123.1)  1.500 ms  0.786 ms  0.742 ms 2  cable1-0.oronmeaz-ar4001.nyroc.rr.com (76.179.16.1)  15.401 ms  73.275 ms  10.571 ms 3  gig1-7.ptldmebng-rtr02.nyroc.rr.com (204.210.64.181)  10.196 ms  13.679 ms  13.375 ms 4  ge-0-3-7.ptldmeags-rtr01.nyroc.rr.com (204.210.65.29)  14.502 ms  38.787 ms  63.480 ms 5  gig6-1-0.ptldmeptl-rtr02.nyroc.rr.com (204.210.64.21)  31.918 ms  30.320 ms  28.616 ms 6  ge-6-0-0.syrcnycsr-rtr03.nyroc.rr.com (24.24.7.145)  101.030 ms  49.754 ms  122.567 ms 7  ae-3-0.cr0.chi10.tbone.rr.com (66.109.6.72)  70.805 ms  108.025 ms  56.544 ms 8  ae-0-0.cr0.chi30.tbone.rr.com (66.109.6.21)  73.575 ms  87.235 ms  116.295 ms 9  ae-4-0.cr0.nyc20.tbone.rr.com (66.109.6.24)  128.303 ms  56.843 ms  101.629 ms10  ae-0-0.pr0.nyc20.tbone.rr.com (66.109.6.157)  61.671 ms  80.365 ms  96.576 ms11  nyc9-core-2.gigabiteth5-1.swip.net (130.244.200.5)  129.290 ms  113.668 ms  66.088 ms12  nyc9-core-1.pos11-0.swip.net (130.244.194.201)  58.673 ms  56.065 ms  119.817 ms13  130.244.218.213 (130.244.218.213)  134.834 ms  195.064 ms  188.019 ms14  * * *15  ams13-core-1.tengigabiteth2-4.swip.net (130.244.52.169)  178.591 ms *  134.867 ms

Re: The NEW "Where does your 6to4 relay address go?" thread!

Wed, 28 Oct 2009 14:14:33 EDT

Napsterbater posted :

said by justbits:

AT+T DSL Static IP, from Chicago, IL. Interesting how it ends up with HE in New York, when there's a HE node in Chicago.

AT&T is handing off to HE in Chicago and HE routes it to NYC which is probably the closest 6to4 they have (they may not have 6to4's in every data center they have ipv6 tunnel servers.)

Tracing route to 192.88.99.1 over a maximum of 30 hops   1    <1 ms    <1 ms    <1 ms  car1-port1.ipv4.napshome.local [10.0.1.6]  2     1 ms     1 ms     1 ms  dslmodem-port1.ipv4.napshome.local [10.0.0.1]  3    12 ms     9 ms     9 ms  h1.152.17.98.dynamic.ip.windstream.net [98.17.152.1]  4   132 ms    42 ms    10 ms  h56.122.90.75.static.ip.windstream.net [75.90.122.56]  5    19 ms    13 ms    13 ms  h70.248.213.151.static.ip.windstream.net [151.213.248.70]  6    16 ms    13 ms    14 ms  h100.254.213.151.static.ip.windstream.net [151.213.254.100]  7    14 ms    13 ms    14 ms  12.88.28.25  8    16 ms    19 ms    16 ms  cr2.attga.ip.att.net [12.122.140.26]  9    15 ms    13 ms    14 ms  ggr3.attga.ip.att.net [12.122.140.149] 10    14 ms    16 ms    13 ms  192.205.36.74 11    15 ms    15 ms    16 ms  sl-crs1-atl-0-4-0-0.sprintlink.net [144.232.18.132] 12    63 ms    44 ms    34 ms  sl-crs1-rly-0-0-5-0.sprintlink.net [144.232.20.177] 13    33 ms    61 ms    39 ms  192.88.99.1 Trace complete.

Re: The NEW "Where does your 6to4 relay address go?" thread!

Thu, 08 Oct 2009 08:22:29 EDT

justbits posted : AT+T DSL Static IP, from Chicago, IL. Interesting how it ends up with HE in New York, when there's a HE node in Chicago.

traceroute to 192.88.99.1 (192.88.99.1), 64 hops max, 40 byte packets 1  EDITED OUT 2  EDITED OUT 3  dist2-vlan54.chcgil.sbcglobal.net (65.42.70.195)  47.926 ms  45.912 ms  45.794 ms 4  bb2-g7-0.chcgil.ameritech.net (151.164.242.210)  46.016 ms  45.684 ms  46.366 ms 5  151.164.99.129 (151.164.99.129)  47.371 ms  46.913 ms  47.041 ms 6  gige-g2-7.core1.chi1.he.net (64.71.140.137)  46.432 ms  46.001 ms  48.027 ms 7  10gigabitethernet2-4.core1.nyc4.he.net (72.52.92.101)  71.381 ms  80.149 ms  74.645 ms 8  10gigabitethernet1-2.core1.nyc1.he.net (72.52.92.46)  82.880 ms  72.432 ms  70.610 ms 9  * * *10  * * *11  *^C

The NEW "Where does your 6to4 relay address go?" thread!

Thu, 08 Oct 2009 07:55:32 EDT

mackey posted : 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 1  juniperm160-02.lax01.calpop.com (64.27.16.17)  1.248 ms   1.153 ms   0.458 ms 2  unknown.calpop.com (206.125.44.254)  1.128 ms   0.646 ms   1.074 ms 3  * * te7-4.ccr01.lax04.atlas.cogentco.com (38.104.83.209)  1.389 ms 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 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 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 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 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 9  sl-bb1v6-sj-0-0-0.sprintlink.net (144.232.3.226)  12.143 ms * *

TX Dedi #1

traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets 1  xx.static.theplanet.com (174.133.168.xxx)  0.437 ms  0.500 ms  0.542 ms 2  et2-7.ibr01.hstntx1.theplanet.com (207.218.223.9)  0.214 ms  0.257 ms  0.305 ms 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 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 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 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 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

TX Dedi #2

traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets 1  xx.static.theplanet.com (70.84.183.xxx)  2.035 ms  2.216 ms  2.436 ms 2  po102.dsr02.dllstx5.theplanet.com (70.87.254.13)  0.921 ms  0.925 ms  1.139 ms 3  po52.dsr02.dllstx3.theplanet.com (70.85.127.109)  1.372 ms  1.607 ms  1.841 ms 4  et5-2.ibr04.dllstx3.theplanet.com (70.87.253.29)  1.329 ms  1.318 ms  1.542 ms 5  10gigabitethernet3-1.core1.dal1.he.net (206.223.118.37)  1.777 ms  2.007 ms  1.981 ms 6  10gigabitethernet5-2.core1.ash1.he.net (72.52.92.62)  36.432 ms  35.680 ms  35.665 ms 7  ash.ipv6.he.net (216.218.229.118)  47.194 ms * *

VA FiOS connection

traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 60 byte packets 1  192.168.10.1 (192.168.10.1)  0.279 ms  0.239 ms  0.211 ms 2  L100.RCMDVA-VFTTP-18.verizon-gni.net (98.117.71.1)  3.843 ms  3.871 ms  3.987 ms 3  G11-1-218.RCMDVA-LCR-02.verizon-gni.net (130.81.129.202)  3.887 ms  3.927 ms  3.970 ms 4  P15-0-0.RCMDVA-LCR-01.verizon-gni.net (130.81.27.64)  8.533 ms  8.659 ms  8.868 ms 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 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 7  0.xe-10-0-0.BR1.IAD8.ALTER.NET (152.63.41.149)  9.642 ms  9.666 ms  9.676 ms 8  sl-st30-ash-0-3-0-0.sprintlink.net (144.232.8.209)  9.726 ms  12.173 ms  12.079 ms 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 ms10  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 ms11  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

PA Comcast connection

traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets 1  73.154.67.1 (73.154.67.1)  11.930 ms  11.893 ms  11.823 ms 2  68.85.76.41 (68.85.76.41)  11.756 ms  11.738 ms  11.713 ms 3  te-9-1-ur01.elizabethtwn.pa.panjde.comcast.net (68.86.209.10)  11.690 ms  13.884 ms  13.899 ms 4  te-9-1-ur01.lowerswatera.pa.panjde.comcast.net (68.86.209.13)  13.859 ms  13.853 ms  13.828 ms 5  68.85.158.129 (68.85.158.129)  13.806 ms  13.781 ms  13.754 ms 6  68.85.158.190 (68.85.158.190)  17.644 ms  12.094 ms  11.347 ms 7  68.85.159.217 (68.85.159.217)  17.316 ms  17.304 ms  17.265 ms 8  be-40-crs01.401nbroadst.pa.panjde.comcast.net (68.86.208.33)  17.874 ms  17.885 ms  17.848 ms 9  pos-1-9-0-0-cr01.mclean.va.ibone.comcast.net (68.86.90.13)  21.644 ms  21.669 ms  21.623 ms10  ash1-core-2.gigabiteth13-1.swip.net (130.244.200.241)  21.593 ms  21.575 ms  21.645 ms11  cbv-core-3.pos0-4-3-0.swip.net (130.244.207.205)  102.760 ms  102.765 ms  102.733 ms12  cbv-core-2.tengigabiteth2-2.swip.net (130.244.52.229)  109.303 ms  102.077 ms  97.794 ms

/mackey