policy: added set vrf and mark matching documentation #1628
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
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.
Change Summary
I added the documentation for the
set vrfoption in policies.I also added the documentation for matching firewall marks.
Related Task(s)
Related PR(s)
vyos/vyos-1x#3740
Backport
Checklist:
Further notes
The way the marks are handled for VRFs/tables has some limitations. It limits the user to a single fwmark per VRF/table. the underlying linux kernel allows e.g. for matching with masks. This would allow it to seperate the 32 Bits (of which only 31 can be matched due to the restrictions in the CLI) into multiple chunks and e.g. use the lower 8 bits for mapping into a VRF while using the upper 24 bits to match to firewall-rules, shapers, etc. By limiting the mapping to a VRF/table to a single mark this is no longer possible.
Judging from the comment here vyos/vyos-1x#3581 (comment) it appears like there is a distinction between "VRF" and "non-VRF" table IDs, however I could not find anything in the documentation that explicitly states that.