| Ticket UUID: | 1245508 | |||
| Title: | NTP handling wrong | |||
| Type: | Bug | Version: | None | |
| Submitter: | dkf | Created on: | 2005-07-26 20:40:36 | |
| Subsystem: | ntp | Assigned To: | patthoyts | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2005-08-18 19:04:42 | |
| Resolution: | Fixed | Closed By: | patthoyts | |
| Closed on: | 2005-08-18 12:04:42 | |||
| Description: |
The handling of (s)ntp by the ntp package is wrong; you can't talk ntp (these days) over tcp and you certainly can't use 'abcd' as a request message! And the package claims to be the time package for [package require], despite being in the ntp dir within the distribution. | |||
| User Comments: |
patthoyts added on 2005-08-18 19:04:41:
Logged In: YES user_id=202636 Fixed the message used for SNTP - as TIME servers don't care what message they get we will send the SNTP request to TIME servers too. The module is for network time protocols (hence the directory name) and the first one implemented was for the TIME (RFC 868) protocol. It turns out that there are insignificant differences between the implementation for TIME and for SNTP (RFC 2030) so I left the package as 'time' and just added a 'getsntp' api. I don't see any good reason to restrict the SNTP usage to UDP - but I have added comments into the man page to point out the likely requirement for UDP. In theory SNTP could be operated over TCP and I note that the services file reserves port 123/tcp and 123/udp for ntp. Added support for ceptcl in addition to tcludp for UDP support. I've checked the new implementation against ntp2a.mcc.ac.uk and ntp.blueyonder.co.uk for SNTP access along with a local server running OpenBSDs minimal NTP server. | |||
Home
Blog
Docs
Downloads
Tickets
Timeline
Branches
Tags
Wiki