Bug #15291
closedIPv6 on ceph.com
0%
Description
I can't connect to ceph.com with IPv6, for several months now. Here a traceroute:
$ mtr -wrc5 ceph.com Start: Mon Mar 28 14:10:22 2016 HOST: nix-pc Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a01:(hidden) 0.0% 5 0.7 0.7 0.7 0.8 0.0 2.|-- gw-(hidden).dus-01.de.sixxs.net 0.0% 5 14.5 13.7 12.9 14.5 0.0 3.|-- ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 4.|-- ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 5.|-- as6939.dus.ipv6.ecix.net 0.0% 5 13.6 16.4 13.6 19.7 2.8 6.|-- 10ge11-4.core1.ams1.he.net 0.0% 5 17.6 20.5 17.6 29.3 4.9 7.|-- 100ge9-1.core1.lon2.he.net 0.0% 5 32.5 34.9 32.5 36.8 1.5 8.|-- 100ge1-1.core1.nyc4.he.net 0.0% 5 90.3 90.8 88.7 93.2 1.4 9.|-- 2001:428:601:e::1 0.0% 5 92.1 91.4 90.6 92.5 0.5 10.|-- 2001:428::205:171:203:158 0.0% 5 101.9 98.4 96.1 101.9 2.6 11.|-- 2001:428:2402:10:0:d:0:2 0.0% 5 95.0 96.0 94.7 99.0 1.7 12.|-- border11-bbnet1.wdc002.pnap.net 0.0% 5 96.6 98.6 96.1 106.9 4.6 13.|-- 2600:c08:2002:d::2 0.0% 5 113.7 101.1 94.1 113.7 7.8 14.|-- ip-2607-f298-5-cc01--1.dreamhost.com 0.0% 5 98.0 98.4 97.2 100.0 0.9 15.|-- ip-2607-f298-5-cc08--2.dreamhost.com 0.0% 5 95.4 99.3 94.5 113.0 7.7 16.|-- 2607:f298:5:110d:f816:3eff:fe79:ad5d 0.0% 5 96.1 96.1 94.9 96.9 0.5 17.|-- ??? 100.0 5 0.0 0.0 0.0 0.0 0.0
ceph.com resolves to 2607:f298:6050:51f3:f816:3eff:fe62:31d3
.
Updated by Dan Mick about 8 years ago
- Status changed from New to Can't reproduce
I can ping6 the host, and the mtr as shown returns me:
[decatur]$ mtr wrc5 ceph.com ip-2607-f298-5-103b--1.dreamhost.com 0.0% 5 2.1 2.4 2.1 2.9 0.3
HOST: decatur Loss% Snt Last Avg Best Wrst StDev
1.|-
2.|-- ip-2607-f298-5-cc03--1.dreamhost.com 0.0% 5 2.0 2.4 2.0 2.6 0.2
3.|-- ip-2607-f298-5-cc08--2.dreamhost.com 0.0% 5 0.3 0.3 0.2 0.3 0.0
4.|-- 2607:f298:5:110d:f816:3eff:fe79:ad5d 0.0% 5 0.4 0.6 0.3 1.3 0.4
5.|-- 2607:f298:6050:51f3:f816:3eff:fe62:31d3 0.0% 5 2.0 4.6 0.6 18.7 7.9
and also IPv6 works from ipv6-test.com
This seems like it must be a client issue at the moment?
Updated by Nix N. about 8 years ago
Directly after your answer I tested again and it worked since then, have checked it a whole day. I'm not sure what was wrong, but I don't think it was client side, because the directly previous hop (16) is already in the 2607:f298:
network and was reachable from here.