puppetlabs-firewall
puppetlabs-firewall copied to clipboard
puppetlabs
Puppet Firewall Module
Now you can not only ``` match_mark => '0x02' ``` but also ``` match_mark => '! 0x02' ```
## Describe the error Writes errors to the console when applying a directory. ## Expected behavior No errors ## Playback actions Run pappet on kubernetes node under AlmaLinux 9.0 with...
## Describe the Bug Our Firewall nightlys are failing at the Post Workflow Status to Slack step. Error message includes: `StatusCodeError: 404 - "channel_not_found"` ## Expected Behavior Post Workflow Status...
With 'firewall { .. }' in a manifest in a kickstart the puppet run always fails with: Error: Could not prefetch firewall provider 'iptables': Execution of '/sbin/iptables-save' returned 1: iptables-save/1.8.4...
For example: ```puppet firewall { '200 http https': dport => [80, 443], proto => 'tcp', destination => ['1.2.3.4', '2.3.4.5'], action => 'accept' } ``` Puppet will only include the first...
## Use Case We are using firewall on hosts which may have programs installed which manage their own firewall rules on the host (fail2ban, Docker, ...). `ignore` on `firewallchain` resources...
Issues have arisen with the --random-fully value on certain RedHat versions. It seem's as if the logic put in around `--random` and `--random-fully` are no longer working. This change should...
When rules with rpfilter are used, then there are warnings like these in the output: `Warning: Puppet::Type::Firewall::ProviderIptables: Skipping unparsable iptables rule: keys (5) and values (6) count mismatch on line:...
## Describe the Bug When running Puppet on an RHEL 8.6 node, the run fails with the following error: ``` Error: Could not prefetch firewall provider 'iptables': Parser error: random...
