tock.umanitoba.ca NTP over IPv6 broken?
Hi Guys: Wondering if tock.umanitoba.ca works for anyone via IPv6? I'm able to ping the system, but NTP gets stuck in INIT state. (3rd line, they don't have revdns setup either for IPv6 I guess) theodore@dev:~$ ntpq -p; ping -c4 tock.umanitoba.ca; ping6 -c4 tock.umanitoba.ca remote refid st t when poll reach delay offset jitter ============================================================================== *time1.mbix.ca .PCS0. 1 u 7 128 377 1.205 0.026 0.201 -2620:10a:800f:: .PPS. 1 u 68 128 377 26.991 0.129 11.834 2620:0:bd0:4001 .INIT. 16 u - 1024 0 0.000 0.000 0.000 +zero.gotroot.ca 30.114.5.31 2 u 73 128 377 26.632 0.023 0.118 +ntp3.torix.ca .PPS. 1 u 1 128 377 24.842 -0.128 11.029 PING tock.umanitoba.ca (192.139.114.77) 56(84) bytes of data. 64 bytes from tock.umanitoba.ca (192.139.114.77): icmp_req=1 ttl=56 time=2.25 ms 64 bytes from tock.umanitoba.ca (192.139.114.77): icmp_req=2 ttl=56 time=1.97 ms 64 bytes from tock.umanitoba.ca (192.139.114.77): icmp_req=3 ttl=56 time=2.22 ms 64 bytes from tock.umanitoba.ca (192.139.114.77): icmp_req=4 ttl=56 time=2.37 ms --- tock.umanitoba.ca ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 1.975/2.207/2.373/0.152 ms PING tock.umanitoba.ca(2620:0:bd0:4001::77) 56 data bytes 64 bytes from 2620:0:bd0:4001::77: icmp_seq=1 ttl=56 time=32.0 ms 64 bytes from 2620:0:bd0:4001::77: icmp_seq=2 ttl=56 time=32.7 ms 64 bytes from 2620:0:bd0:4001::77: icmp_seq=3 ttl=56 time=31.7 ms 64 bytes from 2620:0:bd0:4001::77: icmp_seq=4 ttl=56 time=31.7 ms --- tock.umanitoba.ca ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 31.718/32.067/32.738/0.448 ms -- Theo Baschak BOFH excuse #133: It's not plugged in.
On 14-12-15 11:31 AM, Theodore Baschak wrote:
Wondering if tock.umanitoba.ca works for anyone via IPv6? I'm able to ping the system, but NTP gets stuck in INIT state.
1. I thought the UofM's policy (so far) on IPv6 was basically "Ha, ha, NO" ? 2. Only (S)NTPv4 supports IPv6. Despite the fact that SNTPv4 was standardized in 1996 and NTPv4 in 2010, many sites still only run v3-capable servers. I don't know if either of these items explains your issue, that would have to wait for someone from the UofM who reads this list. -- -Adam Thompson athompso@athompso.net Cell: +1 204 291-7950 Fax: +1 204 489-6515
On 15/12/2014 11:51 AM, Adam Thompson wrote:
On 14-12-15 11:31 AM, Theodore Baschak wrote:
Wondering if tock.umanitoba.ca works for anyone via IPv6? I'm able to ping the system, but NTP gets stuck in INIT state.
1. I thought the UofM's policy (so far) on IPv6 was basically "Ha, ha, NO" ?
If there's an official policy on IPv6, I haven't seen it yet. :) However, I think it's safe to assume that, for the time being at least, the deployment of IPv6 is extremely limited and strictly on a test basis. I certainly wouldn't rely on IPv6 access to any U of M service for production use right now. (It's also interesting that tock's counterpart, tick.umanitoba.ca, doesn't appear to have a AAAA record.)
2. Only (S)NTPv4 supports IPv6. Despite the fact that SNTPv4 was standardized in 1996 and NTPv4 in 2010, many sites still only run v3-capable servers.
I don't know if either of these items explains your issue, that would have to wait for someone from the UofM who reads this list.
The above is my personal opinion, and does not in any way reflect the official position of the U of M. Some settling of contents may occur. Your mileage may vary. Etc. -- Gilbert E. Detillieux E-mail: <gedetil@muug.mb.ca> Manitoba UNIX User Group Web: http://www.muug.mb.ca/ PO Box 130 St-Boniface Phone: (204)474-8161 Winnipeg MB CANADA R2H 3B4 Fax: (204)474-7609
On Dec 15, 2014, at 11:51, Adam Thompson <athompso@athompso.net> wrote:
On 14-12-15 11:31 AM, Theodore Baschak wrote:
Wondering if tock.umanitoba.ca works for anyone via IPv6? I'm able to ping the system, but NTP gets stuck in INIT state.
1. I thought the UofM's policy (so far) on IPv6 was basically "Ha, ha, NO" ?
2. Only (S)NTPv4 supports IPv6. Despite the fact that SNTPv4 was standardized in 1996 and NTPv4 in 2010, many sites still only run v3-capable servers.
I don't know if either of these items explains your issue, that would have to wait for someone from the UofM who reads this list.
The U of M is connected via IPv6 through MRnet; the network core along with with a one ’test’ buildings/networks are full IPv6 dual stack. Tock is an appliance and does have an IPv6 address with ntp version 4 (not SNTP) but I’ve yet to be able to make ntp actually function over IPv6. The vendor claims it works, my experience differs. Theres not really much configuration as the GUI only presents a check box called "Service all IPv6 requests by default.” and that’s been enabled for quite some time. The administrative interface does work fine over IPv6 but ntp apparently does not. I’ve been told not to do any further work on IPv6 so I’ve been poking at tock occasionally in my own time but not to any great extent. Cheers, Dave. -- David Milton - david@dmilton.ca The mind is like a parachute; it only functions when open. - unknown
On 15 Dec 2014, at 13:51, David Milton <david@dmilton.ca> wrote:
The U of M is connected via IPv6 through MRnet; the network core along with with a one ’test’ buildings/networks are full IPv6 dual stack. Tock is an appliance and does have an IPv6 address with ntp version 4 (not SNTP) but I’ve yet to be able to make ntp actually function over IPv6. The vendor claims it works, my experience differs. Theres not really much configuration as the GUI only presents a check box called "Service all IPv6 requests by default.” and that’s been enabled for quite some time. The administrative interface does work fine over IPv6 but ntp apparently does not. I’ve been told not to do any further work on IPv6 so I’ve been poking at tock occasionally in my own time but not to any great extent.
Cheers, Dave.
Thanks for the extremely awesome and detailed response! I forget how I got started on this in the first place, I think I noticed that I'd picked up "tock.umanitoba.ca" (according to revdns) via NTP.org's pool, and then changed my config to use it (of course, since I'm all dual-stacked my system then prefers the V6 address). -- Theo Baschak BOFH excuse #11: magnetic interference from money/credit cards
My understanding was that tick and tock haven't been the U of M's official time servers for many years, and haven't been particularly reliable either. I think if you're looking for a decent local NTP server, ntp.cc.umanitoba.ca would be a better choice. I don't know if it supports IPv6 though. On 12/15/2014 11:31 AM, Theodore Baschak wrote:
Hi Guys:
Wondering if tock.umanitoba.ca works for anyone via IPv6? I'm able to ping the system, but NTP gets stuck in INIT state.
-- Gilles R. Detillieux E-mail: <grdetil@scrc.umanitoba.ca> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. of Physiology and Pathophysiology, Faculty of Health Sciences, Univ. of Manitoba Winnipeg, MB R3E 0J9 (Canada)
participants (5)
-
Adam Thompson -
David Milton -
Gilbert E. Detillieux -
Gilles Detillieux -
Theodore Baschak