puppet nftables

Additionally, the module comes with a basic infrastructure

to hook into different places.

The main configuration file loaded by the nftables service

will be `files/config/puppet.nft`, all other files created

INPUT and OUTPUT to the loopback device is allowed by

default, though you could restrict it later.

Initially puppet deploys all configuration to

`/etc/nftables/puppet-preflight/` and

If and only if successful the configuration will be copied to

the real locations before the service is reloaded.

### nftables::config

Manages a raw file in `/etc/nftables/puppet/${name}.nft`

Use this for any custom table files.

Prepares a chain file as a `concat` file to which you will

be able to add dedicated rules through `nftables::rule`.

chain. It's possible to specify the in-interface name and

out-interface name for the inject rule.

A simple way to add rules to any chain. The name must be:

`CHAIN_NAME-rulename`, where CHAIN_NAME refers to your

[REFERENCE](https://github.com/voxpupuli/puppet-nftables/blob/master/REFERENCE.md),

somebody might have encapsulated a rule definition for you already.

Adds a named set to a given table. It allows composing the

set using individual parameters but also takes raw input

via the content and source parameters.

Allows expressing firewall rules without having to use nftables's language by

adding an abstraction layer a-la-Firewall. It's rather limited how far you can