firewall: T7452: update rule generation for Zone-based firewall

[davi2367]

Change summary

When utilizing the ZBF with VRF, issues occur with outgoing traffic - specifically with ping packets destined for interface on vyos itself.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, renaming)
• Refactoring (no functional changes)
• Migration from an old Vyatta component to vyos-1x, please link to related PR inside obsoleted component
• Other (please describe):

Related Task(s)

https://vyos.dev/T7452

Related PR(s)

How to test / Smoketest result

I added the below entries in netfilter above the default drop, and it solved the issue

oifname "MGMT" counter packets 0 bytes 0 jump NAME_IPV4_LOCAL_TO_MGMT
oifname "MGMT" counter packets 0 bytes 0 return

Checklist:

• I have read the CONTRIBUTING document
• I have linked this PR to one or more Phabricator Task(s)
• I have run the components SMOKETESTS if applicable
• My commit headlines contain a valid Task id
• My change requires a change to the documentation
• I have updated the documentation accordingly

[github-actions]

👍
No issues in PR Title / Commit Title

[davi2367]

On a local VyOS instance ive replaced "/usr/share/vyos/templates/firewall/nftables-zone.j2" with the file in the commit, and corrected some errors. It seems to be working so-far without any issues.

[sarthurdev]

IIRC outbound packets to VRF used the physical interface name.

Ping @nicolas-fort as I think this was something you worked on previously. If you have any feedback here?

[github-actions]

CI integration ❌ failed!

Details

CI logs

• CLI Smoketests (no interfaces) ❌ failed
• CLI Smoketests (interfaces only) ❌ failed
• Config tests ❌ failed
• RAID1 tests ❌ failed
• TPM tests ❌ failed

[davi2367]

IIRC outbound packets to VRF used the physical interface name.

Ping @nicolas-fort as I think this was something you worked on previously. If you have any feedback here?

If need be, one can specify the interfaces to listen use in rules by using the "member interface" instead of "member vrf", i changed the behaviour as both are possible with this approach, and it follows the same approach as earlier commits where both vrf and interface was specified under "interface" :)