On Sat, Jun 30, 2012 at 4:14 AM, Rainer May <[email protected]> wrote: > Alexander Falk schrieb: > > > > However, since it is the same physical machine and a Stratum 1 server > > I know for a fact that it is accurate. Is this an IPv6 networking > > issue with routing or latencies? Or is the monitoring server for IPv6 > > working differently? > > > Same situation here. No matter if IPv6 connectivity is relised natively > or with a tunnel. Therefore I assume that's a routing issue. > > A student here just started to observe differences in routing and > overall connectivity stability between v4 and v6 (I'm curious, and he > needed a bachelor topic anyway :) ) > _______________________________________________ >
I'm in the same apparent boat. Same Stratum-1 Server with both a v4 and v6 connection. The v4 link is running flawlessly, while the v6 link looks like the chart of the S&P500. lol Up some times and Down the others. So obviously the monitoring tool is getting time/connection, but something is causing intermittent issues with v6. Since v4 is running clean, it can't be the server, its gotta be the v6 routing. NOTES: Same NTP Server ------------ v4: http://www.pool.ntp.org/scores/63.251.89.141 v6: http://www.pool.ntp.org/scores/2001:470:7:104::2 But my v6 seems very much alive and without issue. Yesterday I was ssh'd into my box from work via v6 and never had any issues. Personally, the finger "seems" to be pointing at the monitoring server having issues reaching servers via v6 if there appears to be a wide spread issue with other folks. Any clues from the pool masters?
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
