Strange. I suppose I need to do a little inquiry with HE.net. Otherwise I'll just have to throw v6 traffic via my SixXS link. On Jun 27, 2012 12:39 PM, "Rainer May" <[email protected]> wrote:
> Obviously it does not want to talk to me: > > root@www:~# ip -6 a s dev eth0 > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 > inet6 2a00:1828:2000:115::3/64 scope global > valid_lft forever preferred_lft forever > inet6 fe80::216:3eff:fe7c:756c/64 scope link > valid_lft forever preferred_lft forever > root@www:~# ntpdate -d 2001:470:7:104::2 > 27 Jun 18:33:12 ntpdate[15727]: ntpdate [email protected] Sun Oct 17 > 13:35:14 UTC 2010 (1) > transmit(2001:470:7:104::2) > transmit(2001:470:7:104::2) > transmit(2001:470:7:104::2) > transmit(2001:470:7:104::2) > transmit(2001:470:7:104::2) > 2001:470:7:104::2: Server dropped: no data > server 2001:470:7:104::2, port 123 > stratum 0, precision 0, leap 00, trust 000 > refid [2001:470:7:104::2], delay 0.00000, dispersion 64.00000 > transmitted 4, in filter 4 > reference time: 00000000.00000000 Mon, Jan 1 1900 1:00:00.000 > originate timestamp: 00000000.00000000 Mon, Jan 1 1900 1:00:00.000 > transmit timestamp: d395b44e.3a95ce84 Wed, Jun 27 2012 18:33:18.228 > filter delay: 0.00000 0.00000 0.00000 0.00000 > 0.00000 0.00000 0.00000 0.00000 > filter offset: 0.000000 0.000000 0.000000 0.000000 > 0.000000 0.000000 0.000000 0.000000 > delay 0.00000, dispersion 64.00000 > offset 0.000000 > > 27 Jun 18:33:20 ntpdate[15727]: no server suitable for synchronization > found > > > But not only via ntp: > > root@www:~# traceroute6 2001:470:7:104::2 > traceroute to 2001:470:7:104::2 (2001:470:7:104::2), 30 hops max, 80 > byte packets > 1 2a00:1828:2000:115::1 (2a00:1828:2000:115::1) 1.931 ms 1.704 ms > 1.526 ms > 2 inexio1.gw.network.manitu.net (2a00:1828:1000:1001::9) 5.047 ms > 5.004 ms 4.944 ms > 3 30gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1) 7.361 > ms 16.249 ms 16.212 ms > 4 10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1) 20.701 > ms 20.544 ms 20.444 ms > 5 10gigabitethernet7-4.core1.nyc4.he.net (2001:470:0:128::1) 86.158 > ms 86.516 ms 91.885 ms > 6 10gigabitethernet2-3.core1.ash1.he.net (2001:470:0:36::1) 106.932 > ms 99.264 ms 94.931 ms > 7 ordns.he.net (2001:470:20::2) 100.459 ms 100.705 ms 102.465 ms > 8 * * * > 9 * * * > 10 * * * > 11 * * * > 12 * * * > 13 * * * > 14 * * * > 15 * * * > 16 * * * > 17 * * * > 18 * *^C > > And yes, I CAN reach other hosts: > > root@www:~# traceroute6 www.heise.de > traceroute to www.heise.de (2a02:2e0:3fe:100::7), 30 hops max, 80 byte > packets > 1 2a00:1828:2000:115::1 (2a00:1828:2000:115::1) 1.156 ms 1.120 ms > 1.103 ms > 2 inexio1.gw.network.manitu.net (2a00:1828:1000:1001::9) 4.860 ms > 4.845 ms 4.823 ms > 3 te3-1.c101.f.de.plusline.net (2001:7f8::3012:0:1) 7.442 ms 6.751 > ms 7.397 ms > 4 te6-1.c13.f.de.plusline.net (2a02:2e0:1::1e) 6.689 ms 6.657 ms > 6.637 ms > 5 www.heise.de (2a02:2e0:3fe:100::7) 6.604 ms 7.254 ms 6.543 ms > > > So it looks like the route to your server is not propagated (btw, same > situation from a server on a HE.net tunnel) > > AlbyVA wrote: > > > > > > Is anybody having issues with adding a v6 server into the pool via > > the website site? > > I'm trying to add ( 2001:470:7:104::2) and I'm getting this error: > > > > Didn't get an NTP response from 2001:470:7:104::2 > > > > > > Yet, I know my server is working because I can query the following > > via v6 (See Below). > > Also my v4 address (same server) works like a charm > > (godzilla.empire.org <http://godzilla.empire.org> / 63.251.89.141). > > Any ideas? > > > > > >
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
