Am 2013-05-18 01:26, schrieb Ask Bjørn Hansen:
It is in progress now.
Is there some IPv6 routing problem since the migration?
http://www.pool.ntp.org/scores/2a01:4f8:162:51e2::2 vs
http://www.pool.ntp.org/scores/2a02:180:1:1::5b8f:533e
Both servers work without issues via IPv4:
On Saturday, May 18, 2013 at 5:55 AM, Paul Staroch wrote:
Is there some IPv6 routing problem since the migration?
http://www.pool.ntp.org/scores/2a01:4f8:162:51e2::2 vs
http://www.pool.ntp.org/scores/2a02:180:1:1::5b8f:533e
I'm looking into it. I suspect it's unrelated from moving rack.
Am 2013-05-18 16:56, schrieb Ask Bjørn Hansen:
On Saturday, May 18, 2013 at 5:55 AM, Paul Staroch wrote:
Is there some IPv6 routing problem since the migration?
http://www.pool.ntp.org/scores/2a01:4f8:162:51e2::2 vs
http://www.pool.ntp.org/scores/2a02:180:1:1::5b8f:533e
I'm looking into
All seems okay from my Hurricane Electric v6 Tunnel in Ashburn,VA.
http://www.pool.ntp.org/scores/2001:470:8:104::2
traceroute6 to ntppool.net (2607:f238:2::4) from 2001:470:8:104::2, 64 hops
max, 12 byte packets
1 2001:470:8:104::1 0.404 ms 0.308 ms 0.253 ms
2