ansible-role-firewall icon indicating copy to clipboard operation
ansible-role-firewall copied to clipboard

Flush rules for INPUT chain only (for compatibility with docker)

Open vitabaks opened this issue 1 year ago • 5 comments

This pull request refactors the firewall playbook to introduce the ability to flush only the INPUT chains, while leaving other chains (such as DOCKER chains) untouched. This change is made to ensure compatibility with Docker configurations.

The following changes have been made:

  1. Added new variables:
  • firewall_flush_rules_input_nat: Indicates whether to flush the INPUT chain in the 'nat' table.
  • firewall_flush_rules_input_mangle: Indicates whether to flush the INPUT chain in the 'mangle' table.
  • firewall_flush_rules_input_filter: Indicates whether to flush the INPUT chain in the 'filter' table.
  1. Updated the playbook logic:
  • The flush rules for the INPUT chain are now conditioned based on the new variables mentioned above.
  • This change allows selective flushing of the INPUT chains, leaving other chains untouched.

These changes ensure compatibility with Docker configurations and provide more flexibility in managing firewall rules.

vitabaks avatar Jul 19 '23 19:07 vitabaks

This pr 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.

github-actions[bot] avatar Nov 19 '23 18:11 github-actions[bot]

This works pretty well! 👍

etoosamoe avatar Dec 06 '23 15:12 etoosamoe

This PR should fix issues #80 and #82.

kare avatar Dec 13 '23 20:12 kare

@etoosamoe Do you think this PR is ready for a merge?

kare avatar Dec 13 '23 20:12 kare

@etoosamoe Do you think this PR is ready for a merge?

Definitely. It does exactly what it supposed to do - add controls if we want to flush some another chains.

etoosamoe avatar Dec 14 '23 16:12 etoosamoe

This pr 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.

github-actions[bot] avatar Apr 14 '24 21:04 github-actions[bot]

This pr 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.

github-actions[bot] avatar Jun 16 '24 18:06 github-actions[bot]