fix: sort ports and merge adjacent ones in the nft rule #9010
Conversation
This file contains 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
Fixes siderolabs#9009 When building a port interval set, sort the ports and merge adjacent ranges to prevent mismatch on the nftables side. With address sets, this was already the case due to the way IPRange builder works, but ports need a manual implementation. Signed-off-by: Andrey Smirnov <[email protected]>
Unix4ever
approved these changes
Jul 12, 2024
|
/m |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #9009
When building a port interval set, sort the ports and merge adjacent ranges to prevent mismatch on the nftables side.
With address sets, this was already the case due to the way IPRange builder works, but ports need a manual implementation.