|
Ticket ID: SIXXS #2737257 Ticket Status: Remote Problem PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)
connectivity problems from 2001:4830:16ca::/48 ?
![[ca]](/s/countries/ca.gif) Shadow Hawkins on Monday, 04 October 2010 19:50:40
I have connectivity issues from 2001:4830:16ca::/48 to 2001:550:901:f001::147.
Both can see
kingsmere-[~] mcr 10052 %traceroute6 -n 2001:550:901:f001::147
traceroute to 2001:550:901:f001::147 (2001:550:901:f001::147) from 2001:4830:16ca:1:224:21ff:fea7:5e27, port 33434, from port 46345, 30 hops max, 60 byte packets
1 2001:4830:16ca:1::1 1.503 ms 0.975 ms 0.465 ms
2 2001:4830:1600:1df::1 34.452 ms 34.439 ms 35.263 ms
3 2001:4830:e6:7::1 35.305 ms 35.267 ms 35.008 ms
4 2001:4810:0:100::1 36.958 ms 35.824 ms 35.241 ms
5 2001:4810::1:4:2 44.263 ms 44.514 ms 43.156 ms
6 2001:668:0:3::8000:1 36.753 ms 36.483 ms 35.106 ms
7 2001:668:0:2::1:1291 36.501 ms 35.122 ms 35.526 ms
STARS from thence on.
yet both ends can see sites such as www.kame.net. I do not have visibility
as to what is wrong, I don't have enough info, and there looking glasses (other than sixxs') seem to mostly have died.
The fault may be my upstream, COGENT's.
2001:550:901::/48 is my prefix in a montreal datacentre where I can get native IPv6.
kingsmere-[~] mcr 10052 %traceroute6 www.kame.net
traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001:4830:16ca:1:224:21ff:fea7:5e27, port 33434, from port 62722, 30 hops max, 60 byte packets
1 pink.gatineau.credil.org (2001:4830:16ca:1::1) 2.580 ms 0.971 ms 0.458 ms
2 gw-480.qas-01.us.sixxs.net (2001:4830:1600:1df::1) 34.445 ms 33.587 ms 33.310 ms
3 sixxs-gw.hotnic.us.occaid.net (2001:4830:e6:7::1) 34.863 ms 34.631 ms 34.298 ms
4 xe-0.equinix.asbnva01.us.bb.gin.ntt.net (2001:504:0:2::2914:1) 50.519 ms 35.077 ms 36.781 ms
5 ae-0.r21.asbnva01.us.bb.gin.ntt.net (2001:418:0:2000::229) 35.084 ms 191.983 ms 33.976 ms
6 as-3.r20.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::23a) 113.946 ms 113.139 ms 113.475 ms
7 as-2.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::ce) 236.527 ms 236.438 ms 237.035 ms
8 po-1.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::10e) 230.015 ms 229.830 ms 232.172 ms
9 ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:5000::82) 222.307 ms 226.393 ms 222.176 ms
10 ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 226.417 ms 222.134 ms 221.475 ms
11 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 247.885 ms 246.453 ms 247.101 ms
12 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 242.776 ms 241.851 ms 242.810 ms
13 2001:200:dff:fff1:216:3eff:feb1:44d7 (2001:200:dff:fff1:216:3eff:feb1:44d7) 238.067 ms 238.708 ms 237.114 ms
ns3-[~] mcr 10001 %traceroute6 www.kame.net
traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 40 byte packets
1 2001:550:901:82::253 (2001:550:901:82::253) 0.331 ms 0.571 ms 0.556 ms
2 2001:4830:1690:f011::1 (2001:4830:1690:f011::1) 0.275 ms 0.520 ms 0.505 ms
3 (2001:550:2:6::5) 86.947 ms 86.933 ms 87.531 ms
4 te0-2-0-1.ccr22.ymq02.atlas.cogentco.com (::ffff:154.54.7.117) 74.990 ms 74.977 ms 75.204 ms
5 te0-2-0-6.ccr21.ord01.atlas.cogentco.com (::ffff:154.54.30.238) 75.185 ms te0-0-0-6.ccr22.ord01.atlas.cogentco.com (::ffff:154.54.28.5) 74.925 ms te0-0-0-6.ccr21.ord01.atlas.cogentco.com (::ffff:154.54.28.1) 74.912 ms
6 te0-1-0-3.ccr21.mci01.atlas.cogentco.com (::ffff:154.54.25.81) 75.141 ms te0-3-0-0.ccr21.mci01.atlas.cogentco.com (::ffff:154.54.7.185) 75.002 ms 75.240 ms
7 te0-2-0-2.ccr21.sfo01.atlas.cogentco.com (::ffff:154.54.6.161) 75.193 ms 75.182 ms te0-3-0-3.ccr21.sfo01.atlas.cogentco.com (::ffff:154.54.24.109) 75.164 ms
8 2001:550::112 (2001:550::112) 172.741 ms 74.405 ms 74.388 ms
9 2001:550:3::1 (2001:550:3::1) 74.860 ms 74.847 ms 75.122 ms
10 2001:550:3::2 (2001:550:3::2) 75.108 ms 75.450 ms 75.433 ms
11 ae-7.r20.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::2ed) 74.765 ms ae-8.r21.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::351) 74.746 ms 104.591 ms
12 as-1.r20.osakjp01.jp.bb.gin.ntt.net (2001:218:0:2000::7e) 188.544 ms 188.504 ms 188.486 ms
13 po-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::116) 181.240 ms 185.918 ms 181.139 ms
14 po-1.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::10e) 198.100 ms 198.086 ms ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:5000::82) 186.965 ms
15 ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:5000::82) 201.014 ms 201.001 ms 194.829 ms
16 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 185.991 ms 185.978 ms 180.989 ms
17 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 188.900 ms 188.979 ms 188.958 ms
18 cloud-net1.wide.ad.jp (2001:200:0:1c0a:218:8bff:fe43:d1d0) 196.837 ms 196.824 ms 196.809 ms
19 2001:200:dff:fff1:216:3eff:feb1:44d7 (2001:200:dff:fff1:216:3eff:feb1:44d7) 188.432 ms 195.143 ms 180.801 ms
connectivity problems from 2001:4830:16ca::/48 ?
Shadow Hawkins on Monday, 04 October 2010 19:55:18
From another of my tunnels that terminates on usqua01 (same POP)
mcr@sns:~$ traceroute6 ns3.isp.novavision.ca
traceroute to ns3.isp.novavision.ca (2001:550:901:82::247), 30 hops max, 40 byte packets
1 gw-41.qas-01.us.sixxs.net (2001:4830:1600:28::1) 10.400 ms 10.329 ms 11.585 ms
2 sixxs-gw.hotnic.us.occaid.net (2001:4830:e6:7::1) 12.005 ms 11.975 ms 11.943 ms
3 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 13.467 ms 13.442 ms 13.404 ms
4 carpathia-gw.hotnic.net (2001:4810::1:4:2) 21.880 ms 21.851 ms 21.816 ms
5 xe-1-1-0-158.was12.ip6.tinet.net (2001:668:0:3::8000:1) 13.271 ms 13.241 ms 13.207 ms
6 xe-2-0-0.was12.ip6.tinet.net (2001:668:0:2::1:1291) 66.920 ms 11.475 ms 11.436 ms
7 * * *
8 * * *
9 * * *
connectivity problems from 2001:4830:16ca::/48 ?
Shadow Hawkins on Monday, 04 October 2010 19:55:57
A traceroute from usdal01 (which works):
mcr@relay:~$ traceroute6 ns3.isp.novavision.ca
traceroute to ns3.isp.novavision.ca (2001:550:901:82::247), 30 hops max, 40 byte packets
1 gw-226.dal-01.us.sixxs.net (2001:1938:80:e1::1) 4.000 ms 4.000 ms 4.000 ms
2 2001:4de0:1000:a3::1 (2001:4de0:1000:a3::1) 4.000 ms 4.000 ms 4.000 ms
3 2001:4de0:1000:28::1 (2001:4de0:1000:28::1) 64.003 ms 64.003 ms 64.003 ms
4 2001:450:2002:96::1 (2001:450:2002:96::1) 160.009 ms 160.009 ms 160.009 ms
5 2001:450:2008:1029::2 (2001:450:2008:1029::2) 160.009 ms 164.009 ms 160.009 ms
6 te0-0-0-1.ccr21.ord01.atlas.cogentco.com (::ffff:154.54.1.1) 184.010 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com (::ffff:154.54.5.1) 184.010 ms te0-4-0-1.ccr21.ord01.atlas.cogentco.com (::ffff:154.54.25.65) 184.010 ms
7 te0-3-0-6.ccr22.ymq02.atlas.cogentco.com (::ffff:66.28.4.138) 184.010 ms 188.010 ms te0-2-0-7.ccr22.ymq02.atlas.cogentco.com (::ffff:154.54.28.6) 192.011 ms
8 (2001:550:2:6::5) 192.011 ms 192.011 ms 192.011 ms
9 (2001:550:2:6::6) 188.010 ms 192.011 ms 192.011 ms
10 ns3.isp.novavision.ca (2001:550:901:82::247) 192.011 ms 192.011 ms 192.011 ms
mcr@relay:~$ exit
State change: remoteproblem
The state of this ticket has been changed to remoteproblem
connectivity problems from 2001:4830:16ca::/48 ?
# traceroute6 -n 2001:550:901:f001::147
traceroute to 2001:550:901:f001::147 (2001:550:901:f001::147), 30 hops max, 80 byte packets
1 2001:4978:f:403::1 55.723 ms 55.713 ms 55.708 ms
2 2001:4978:1:400::ffff 142.502 ms 142.506 ms 142.504 ms
3 2001:590::451f:6f19 59.614 ms 59.610 ms 59.536 ms
4 2001:450:2002:1c::1 59.428 ms 59.435 ms 59.432 ms
5 2001:450:2008:1029::2 60.325 ms 60.349 ms 60.299 ms
6 ::ffff:154.54.25.65 81.240 ms ::ffff:154.54.5.1 77.650 ms ::ffff:154.54.6.209 77.574 ms
7 ::ffff:66.28.4.138 77.512 ms ::ffff:154.54.28.6 76.836 ms 76.780 ms
8 2001:550:2:6::5 156.672 ms 157.637 ms 156.652 ms
9 2001:550:901:f001::147 77.624 ms 76.917 ms 76.896 ms
Hop 6 & 7 seem to be compatible IPv6 addresses, that is quite bad, those should never ever appear on the wire. somebody really needs to be kicked quite hard. Most likely some kind of 6PE setup gone horribly wrong.
154.54.6.209 is supposed to be an address in Mauritius, that is Africa, which it does not seem to be based on the latency.
66.28.4.138 is an address inside Cogent.
I am going to blame a transit for this. I'll try to find someone from Cogent here at NANOG who can explain the above and of course get it fixed. Hmmm apparently they do not visit NANOG according to the Attendee list, thus I'll try and find somebody who has a direct tech contact instead.
|
![[ch]](/s/countries/ch.gif)
on Monday, 04 October 2010 20:06:36
Posting is only allowed when you are