Draft
Conversation
Member
|
The UDP approach is probably the simplest one. Done properly it can hole punch through firewalls on the client side. NTP and PTP are tempting from a standardization perspective but that does levy a complexity cost on installation. |
Member
|
Yeah, so that likely means a revival/reboot of #7007. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Looking to start an exploratory PR on improving time synchronization for NT4, specifically targeted toward systemcore development.
Two options on the table that I'll take a look at:
Option 1 would be nice if we could avoid reinventing the wheel, but critically implies it's possible to run a small NTP server on all hardware that ntcore supports. More research to come.