Closed renepardon closed 1 year ago
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
nothing?
This issue is no longer marked for closure.
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
Unstale
This issue is no longer marked for closure.
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
...
This issue is no longer marked for closure.
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.
Would be nice to have a list of IP's we can explicitly block through the iptable configuration. There are some known IP's which are known for being evil.
Also it would be nice to set some default rules like with
firewall_additional_rules
. For example call itfirewall_default_rules
. This way I can set some global defaults for all hosts like dropping all INPUT/FORWARD requests by default and allowing loopback and ping replice but usingfirewall_additional_rules
to create host specific rules.