T6841: firewall: improve config parsing for ZBF when using VRFs and interfaces attached to VRFs #4180
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
Improve config parsing for ZBF when using VRFs and interfaces attached to VRFs
Types of changes
Related Task(s)
Related PR(s)
Component(s) name
firewall
Proposed changes
For zone based firewall, everything is related to matching inbound and outbound interface. The problem is that in Linux, if an interface is attached to a non-default VRF, then:
Before this PR, what was written under
set firewall zone <zone> interface <iface>
was exactly written for inbound|outbound interface in nftables.Now we have provide more options so we can specify
interface name
andinterfave vrf
while defining interfaces in a zone.interface name <iface>
--> it still writes exactly that interfaces for inbound|outbound interface in nftablesinterface vrf <vrf_name>
--> in nftables it writes:How to test
Smoketest result
Checklist: