Add IPv4 preference support#93
Open
martinreichart wants to merge 1 commit intoMobileNativeFoundation:mainfrom
Open
Add IPv4 preference support#93martinreichart wants to merge 1 commit intoMobileNativeFoundation:mainfrom
martinreichart wants to merge 1 commit intoMobileNativeFoundation:mainfrom
Conversation
Adds an option to prefer IPv4 addresses for querying if both IPv4 and IPv6 addresses are resolved. Signed-off-by: Martin Fitzka-Reichart <martin.reichart@caseapps.at>
Contributor
|
Sorry for the delay, not a big fan of this. The way this is usually implemented (happy eye balls, etc) is to prioritize one over the other but not shut down one category. One solution could be to sort the dns results by preferred category and pick the result of the first N successful ones, regardless if they are ipv4 or 6. could have a [ |
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
2 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.
In our tests with Austrian time servers we often see that using IPv6 addresses results in much slower query times (consistently 10 seconds instead of ~4 with only IPv4).
This PR adds a new parameter to the Clock.sync call and NTPClient to allow the preference of IPv4 addresses if both IPv4 and IPv6 addresses are resolved.