Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chrony: Allow filtering for outgoing NTP servers #139

Merged
merged 1 commit into from
Jul 11, 2022

Conversation

bastelfreak
Copy link
Member

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

@bastelfreak bastelfreak added the enhancement New feature or request label Jul 8, 2022
@bastelfreak bastelfreak self-assigned this Jul 8, 2022
manifests/rules/out/chrony.pp Outdated Show resolved Hide resolved
manifests/rules/out/chrony.pp Outdated Show resolved Hide resolved
manifests/rules/out/chrony.pp Outdated Show resolved Hide resolved
manifests/rules/out/chrony.pp Outdated Show resolved Hide resolved
@bastelfreak
Copy link
Member Author

@traylenator could you please take a look again? I was refactoring this while you reviewed. I now create a single rule for all IPv6 addresses and one for all IPv4 addresses. I don't think an IP set is appropriate because usually people won't have hundreds of NTP servers to talk to on the one side, and on the other the set would increase the complexity.

@traylenator
Copy link
Collaborator

@traylenator could you please take a look again? I was refactoring this while you reviewed. I now create a single rule for all IPv6 addresses and one for all IPv4 addresses. I don't think an IP set is appropriate because usually people won't have hundreds of NTP servers to talk to on the one side, and on the other the set would increase the complexity.

For sure the single rule is good.

@bastelfreak bastelfreak merged commit df90595 into voxpupuli:master Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants