Implement complex traffix steering configuration requirements #557
Conversation
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
One can now manage the type of the rule (which is unicast by default). This allows to manage exotic - but used in the wild - rule like blackholes.
It may be used later on in some cases like virtual IPs set by an external tool (eg. keepalived)
…cation One can now fine-tune IP rules using input or output interfaces. One use-case is to catch locally-generated trafic by setting 'iif' to 'lo'
5 tasks
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.
Description
This pull request introduces support for enhanced routing policy rules in Netplan, specifically adding support for type, iif (input interface), and oif (output interface) parameters in routing policy configurations. The changes enable more granular control over network traffic routing and support advanced routing scenarios.
The pull request implement and test the new routing policy features:
Added type scalar to routing-policy specification in the YAML schema
Implemented parsing and validation for rule types in the core parser
Enhanced test coverage with test cases
Added iif (input interface) and oif (output interface) scalars to routing-policy specification
Implemented parsing logic for interface-based routing rules
Enhanced test coverage with test cases
NetworkManager & networkd backend integration of these new items
Fixed IPv4 link-local method handling to avoid unnecessary configuration when not explicitly requested
Corrected rule generation logic to ensure proper rule application
These changes enhance Netplan's routing capabilities, enabling admins to:
Some of theses features are requested in Launchpad bug #1798417
Checklist
make checksuccessfully.make check-coverage).