aboutsummaryrefslogtreecommitdiff
path: root/REFERENCE.md
AgeCommit message (Collapse)Author
2020-04-21by default dont log dropped packetsTim Meusel
2020-04-21make dropping of pakets marked as invalid optionalTim Meusel
2020-04-21use dedicated conntrack parametersFabien COMBERNOUS
2020-04-09cleanup puppet-strings documentationTim Meusel
2019-10-01implement ipset supportTim Meusel
2019-10-01update docker firewalling exampleTim Meusel
2019-09-18move common from hiera data values to init.ppFabien COMBERNOUS
2019-09-13fix kernel incompatibilitiesThore Bödecker
Certain kernel modules and thus iptables functionality was introduced at later releases, so we need to properly reflect that in our default chain initialization procedure. `INPUT` chain for `nat` table was introduced with 2.6.36 `ip6table_nat` kernel module for NAT functionality with IPv6 was introduced with 3.17 This commit implements the required conditional constraints and includes the rspec tests to validate it.
2019-09-13enhance puppet-strings documentationTim Meusel
2019-09-12Merge pull request #68 from foxxx0/collect-chains-from-hieraTim Meusel
expose parameter to initialize custom chains
2019-09-11expose parameter to initialize custom chainsThore Bödecker
Previously it was not possible to define custom chains with parameter, e.g. in order to collect them from hiera. This commit adds this functionality, just like it was already in place for ferm::rules.
2019-09-11allow using an array for $protoThore Bödecker
This enables defining ferm::rule with multiple protocols at once, because using 'all' for $proto does not allow using $dport/$sport.
2019-09-11add ability to define rules in tables != filterThore Bödecker
Previously it was neither possible to properly define custom chains nor to define rules in tables other than the default filter table. For various legitimate reasons it can be required to define rules in the raw, nat or mangle tables, e.g. to use NOTRACK or to configure DNAT/SNAT/MASQUERADE. Additionally it might come in handy to define custom chains to group certain rules and allow a more efficient evaluation for incoming packets by not cramming all rules into the filter/INPUT chain so that (worst-case) all packets need to traverse and evaluate all rules. I have tried to maintain backwards compatibility and to not change default filenames/paths so that it won't result in leftover obsolete unmaged files from previous versions of this module. In order to improve the naming schema the rule $policy has been renamed to $action, however both parameters are available and optional now, with some sanity checks that require at most one of them and issueing a warning() for users of the now deprecated $policy parameter. All previous tests have been adapted to the changes, a long with an additional set of tests for the new feature. Fixes #61
2019-09-02allow preserving of chains in tablesThore Bödecker
2019-09-01Add Debian 10 support & make configdirectory configureableTim Meusel
2019-08-31enhance puppet-strings documentationTim Meusel
2019-07-11generate REFERENCE.mdTim Meusel
2019-04-05generate REFERENCE.mdTim Meusel
2019-03-06regenerate REFERENCE.mdTim Meusel
2019-01-24permit to choose ipv4, ipv6 or bothFabien COMBERNOUS
2018-12-19Simplify puppet-strings documentationTim Meusel