GitHub puppet-nftables

Puppet Module to manage nftables firewall rules.

modulesync 7.4.0

<!--
Thank you for contributing to this project!

• This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
• Please check that here is no existing issue or PR that addresses your problem.
• Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

Allow netdev as table family in defined type nftables::chain

Hi all, we would like to use this module in combination with the netdev table family type.

Are there any objections?

This Pull Request (PR) fixes the following issues

n/a.

This patchset adds a new parameter to the main class to activate a mechanism that will invoke systemctl reload nftables during the Puppet run if manual changes to the in-memory ruleset are detected.

To accomplish this, the systemd unit in charge of nftables is configured to write a hash of the in-memory ruleset right after starting/reloading. During the Puppet run, the hash of the current rule set is compared to the one previously stored. If the hash differs then systemctl reload nftables is executed to flush manual changes.

Fixes #113

<!--
Thank you for contributing to this project!

• This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
• Please check that here is no existing issue or PR that addresses your problem.
• Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

Pull Request (PR) description

Correction of a too general regex concerning bridge names.

Some bridges could be tagged, for example br123:0, and then could be taken by the regexp, generating an invalid config and dropping error : syntax error, unexpected colon, expecting newline or semicolon.

This Pull Request (PR) fixes the following issues

n/a

This could be considered a breaking change. I don't mind keeping it open until the next major release.

<!--
Thank you for contributing to this project!

• This project has a Contributor Code of Conduct: https://voxpupuli.org/coc/
• Please check that here is no existing issue or PR that addresses your problem.
• Our vulnerabilities reporting process is at https://voxpupuli.org/security/

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Pull Request (PR) description

I know the whole concept of nat and IPv6 can seem a bit odd, but I am indeed using it. Having a source nat rule that parallels the snat4 rule would suit me well.

Warning: This is mostly a copy and paste job, so there may be some comedy hiding somewhere.

This Pull Request (PR) fixes the following issues

n/a