SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3066361
Ticket Status: Remote Problem

PoP: frmrs01 - Jaguar Network SARL (Marseille)

Can not reach kame.net, isc.org, nanog.org via IPv6
[fr] Shadow Hawkins on Saturday, 20 November 2010 18:14:46
Hello, I can not reach, the following web servers via IPv6: www.kame.net www.nanog.org www.isc.org At least kame.net worked previoulsy, I used it to test my IPv6 connectivity. I can reach www.google.com and www.arin.net and sixxs.net. Traceroutes: # traceroute6 -T -p 80 www.kame.net traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 40 byte packets 1 gw-277.mrs-01.fr.sixxs.net (2a01:240:fe00:114::1) 67.891 ms 71.021 ms 71.966 ms 2 sixxs-gw.cust.ipv6.jaguar-network.net (2a01:240:202::1) 75.235 ms 78.204 ms 79.411 ms 3 fe3-1.ar01.mar01.ipv6.jaguar-network.net (2a01:240:200:1::1) 80.584 ms 82.004 ms 84.271 ms 4 * * * 5 r1ams1.ce.init7.net (2001:7f8:1::a501:3030:1) 114.364 ms 116.249 ms 118.710 ms 6 ge-0.ams-ix.amstnl02.nl.bb.gin.ntt.net (2001:7f8:1::a500:2914:1) 118.706 ms 88.985 ms 89.292 ms 7 as-4.r21.tokyjp01.jp.bb.gin.ntt.net (2001:418:0:2000::16) 369.349 ms 367.428 ms 369.113 ms 8 po-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::116) 358.020 ms 356.747 ms 357.959 ms 9 * * * 10 * * * ... 30 * * * # traceroute6 -T -p 80 www.nanog.org traceroute to www.nanog.org (2001:48a8:6880:95::21), 30 hops max, 40 byte packets 1 gw-277.mrs-01.fr.sixxs.net (2a01:240:fe00:114::1) 65.560 ms 67.506 ms 70.003 ms 2 sixxs-gw.cust.ipv6.jaguar-network.net (2a01:240:202::1) 71.746 ms 76.385 ms 78.518 ms 3 fe3-1.ar01.mar01.ipv6.jaguar-network.net (2a01:240:200:1::1) 78.712 ms 81.242 ms 82.869 ms 4 * * * 5 he.ipv6.panap.fr (2001:860:0:6::6939:1) 101.005 ms 116.673 ms 116.765 ms 6 10gigabitethernet1-3.core1.lon1.he.net (2001:470:0:42::1) 134.472 ms 87.076 ms 87.703 ms 7 10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1) 152.566 ms 153.886 ms 153.291 ms 8 10gigabitethernet1-2.core1.chi1.he.net (2001:470:0:4e::1) 177.144 ms 178.172 ms 178.690 ms 9 equinix-V6-exchange-chi.merit.edu (2001:504:0:4::237:1) 181.434 ms 177.764 ms 178.112 ms 10 * * * 11 * * * ... 30 * * * # traceroute6 -T -p 80 www.isc.org traceroute to www.isc.org (2001:4f8:0:2::d), 30 hops max, 40 byte packets 1 gw-277.mrs-01.fr.sixxs.net (2a01:240:fe00:114::1) 64.341 ms 67.539 ms 70.156 ms 2 sixxs-gw.cust.ipv6.jaguar-network.net (2a01:240:202::1) 72.207 ms 74.685 ms 75.815 ms 3 fe3-1.ar01.mar01.ipv6.jaguar-network.net (2a01:240:200:1::1) 77.732 ms 80.542 ms 82.433 ms 4 * * * 5 he.ipv6.panap.fr (2001:860:0:6::6939:1) 110.641 ms 111.879 ms 111.958 ms 6 10gigabitethernet1-3.core1.lon1.he.net (2001:470:0:42::1) 127.813 ms 85.733 ms 86.427 ms 7 10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1) 152.785 ms 152.000 ms 164.147 ms 8 10gigabitethernet1-2.core1.chi1.he.net (2001:470:0:4e::1) 176.386 ms 174.933 ms 176.362 ms 9 * * * 10 * * * ... 30 * * * Please find the details of my configuration: # uname -a Linux glouton 2.6.30-bpo.1-686 #1 SMP Sat Jul 18 22:19:04 UTC 2009 i686 GNU/Linux #ifconfig sixxs sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: 2a01:240:fe00:114::2/64 Scope:Global inet6 addr: fe80::40:fe00:114:2/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1 RX packets:73147 errors:0 dropped:0 overruns:0 frame:0 TX packets:57354 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:69706816 (66.4 MiB) TX bytes:5235639 (4.9 MiB) # route -6 Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If 2a01:240:fe00:114::/64 :: U 256 0 1 sixxs fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 sixxs ::/0 2a01:240:fe00:114::1 UG 1024 0 9301 sixxs ::/0 :: !n -1 1 23952 lo ::1/128 :: Un 0 1 963 lo 2a01:240:fe00:114::2/128 :: Un 0 1 73147 lo fe80::40:fe00:114:2/128 :: Un 0 1 0 lo fe80::224:21ff:fe5a:32d8/128 :: Un 0 1 0 lo ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 sixxs ::/0 :: !n -1 1 23952 lo Pascal (PDK5-SIXXS)
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 21 November 2010 00:03:00
Message is Locked
The state of this ticket has been changed to remoteproblem
Can not reach kame.net, isc.org, nanog.org via IPv6
[ch] Jeroen Massar SixXS Staff on Sunday, 21 November 2010 00:06:16
All very remote networks over who we do not have any control or view of what their routing decisions are. No lookingglasses or similar tools are available in those networks thus there is little we can do.
Can not reach kame.net, isc.org, nanog.org via IPv6
[fr] Shadow Hawkins on Sunday, 21 November 2010 12:21:37
I fully understand. It makes me wonder what is the state of IPv6 routing stability and sites reachabitlity. It is hard to tell my employer that we must invest on IPv6 under such conditions. I will try to contact the entities that manage the routers where the routes fail. However it seems that the ARIN WHOIS database is less helpful than the RIPE one. I will keep you informed once the issue is resolved. Do you want to close the ticket (as it is not under your control) or keep it opened just for information ? Regards.
Can not reach kame.net, isc.org, nanog.org via IPv6
[fr] Shadow Hawkins on Tuesday, 23 November 2010 22:42:34
I informed EQUINIX and HE of the problem. HE answered me that they were not able to reproduce the problem today and indeed everything works now. I did not get any answer from EQUINIX. Anyway the problem is solved now. We can close the ticket. Regards, Pascal.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker