alanorth/ansible-personal
1
0
Fork 0
Code Issues 4 Pull Requests Projects Releases Wiki Activity
e68bbb5055
ansible-personal/roles/common/tasks/firewall_Debian.yml

61 lines
2.0 KiB
YAML
Raw Normal View History

Initial commit Signed-off-by: Alan Orth <alan.orth@gmail.com>
2014-08-16 23:35:57 +02:00
---
roles/common: Add firewalld support Needed in Ubuntu 15.04 where iptables-persistent is going away. I have added translations of the current IPv4 and IPv6 iptables rules. Signed-off-by: Alan Orth <alan.orth@gmail.com>
2015-06-07 11:42:03 +02:00
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html
2018-04-26 15:58:35 +02:00
- block:
roles/common: Add support for fail2ban This is active banning of IPs that are brute forcing login attempts to SSH, versus the passive banning of 10,000 abusive IPs from the abuseipdb.com blacklist. For now I am banning IPs that fail to log in successfully more than twelve times in a one-hour period, but these settings might change, and I can override them at the group and host level if needed. Currently this works for CentOS 7, Ubuntu 16.04, and Ubuntu 18.04, with minor differences in the systemd configuration due to older versions on some distributions. You can see the status of the jail like this: # fail2ban-client status sshd Status for the jail: sshd |- Filter | |- Currently failed: 0 | |- Total failed: 0 | `- Journal matches: _SYSTEMD_UNIT=sshd.service + _COMM=sshd `- Actions |- Currently banned: 1 |- Total banned: 1 `- Banned IP list: 106.13.112.20 You can unban IPs like this: # fail2ban-client set sshd unbanip 106.13.112.20
2019-10-26 16:36:07 +02:00
- name: Set Debian firewall packages
set_fact:
debian_firewall_packages:
- firewalld
- tidy
- fail2ban
- python3-systemd # for fail2ban systemd backend
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html
2018-04-26 15:58:35 +02:00
- name: Install firewalld and deps
roles/common: Bump version checks to Debian 9
2019-10-26 16:37:27 +02:00
when: ansible_distribution_major_version is version_compare('9', '>=')
roles/common: Add support for fail2ban This is active banning of IPs that are brute forcing login attempts to SSH, versus the passive banning of 10,000 abusive IPs from the abuseipdb.com blacklist. For now I am banning IPs that fail to log in successfully more than twelve times in a one-hour period, but these settings might change, and I can override them at the group and host level if needed. Currently this works for CentOS 7, Ubuntu 16.04, and Ubuntu 18.04, with minor differences in the systemd configuration due to older versions on some distributions. You can see the status of the jail like this: # fail2ban-client status sshd Status for the jail: sshd |- Filter | |- Currently failed: 0 | |- Total failed: 0 | `- Journal matches: _SYSTEMD_UNIT=sshd.service + _COMM=sshd `- Actions |- Currently banned: 1 |- Total banned: 1 `- Banned IP list: 106.13.112.20 You can unban IPs like this: # fail2ban-client set sshd unbanip 106.13.112.20
2019-10-26 16:36:07 +02:00
apt: pkg={{ debian_firewall_packages }} state=present
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html
2018-04-26 15:58:35 +02:00
roles/common: Use iptables backend for firewalld on Debian For some reason the nftables set support in firewalld doesn't seem to be working. I see that sets (aka ipsets in nftables lingo) are created, but they are empty. For now I will just leave these tasks as they are to revert the behavior on current hosts (should do no change on new installed, as the regexp won't match).
2019-10-26 19:34:25 +02:00
- name: Use iptables backend in firewalld
roles/common: Use nftables firewalld backend on Debian 10 nftables is the iptables replacement. There is support for nftables in firewalld since v0.6.0. See: https://firewalld.org/2018/07/nftables-backend
2019-10-18 18:02:17 +02:00
when: ansible_distribution_major_version is version_compare('10', '>=')
lineinfile:
dest: /etc/firewalld/firewalld.conf
roles/common: Use iptables backend for firewalld on Debian For some reason the nftables set support in firewalld doesn't seem to be working. I see that sets (aka ipsets in nftables lingo) are created, but they are empty. For now I will just leave these tasks as they are to revert the behavior on current hosts (should do no change on new installed, as the regexp won't match).
2019-10-26 19:34:25 +02:00
regexp: '^FirewallBackend=nftables$'
line: 'FirewallBackend=iptables'
roles/common: Use nftables firewalld backend on Debian 10 nftables is the iptables replacement. There is support for nftables in firewalld since v0.6.0. See: https://firewalld.org/2018/07/nftables-backend
2019-10-18 18:02:17 +02:00
notify:
- restart firewalld
roles/common: Use individual calls with firewalld Seems to work around an issue when firewalld is using the nftables backend with iptables 1.8.2 on Debian 10. Alternatively I could go back to using the iptables backend... hmm. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914694
2019-10-18 21:49:29 +02:00
# firewalld seems to have an issue with iptables 1.8.2 when using the nftables
# backend. Using individual calls seems to work around it.
# See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931722
- name: Use individual iptables calls
when: ansible_distribution_major_version is version_compare('10', '>=')
lineinfile:
dest: /etc/firewalld/firewalld.conf
roles/common: Use iptables backend for firewalld on Debian For some reason the nftables set support in firewalld doesn't seem to be working. I see that sets (aka ipsets in nftables lingo) are created, but they are empty. For now I will just leave these tasks as they are to revert the behavior on current hosts (should do no change on new installed, as the regexp won't match).
2019-10-26 19:34:25 +02:00
regexp: '^IndividualCalls=yes$'
line: 'IndividualCalls=no'
roles/common: Use individual calls with firewalld Seems to work around an issue when firewalld is using the nftables backend with iptables 1.8.2 on Debian 10. Alternatively I could go back to using the iptables backend... hmm. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914694
2019-10-18 21:49:29 +02:00
notify:
- restart firewalld
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html
2018-04-26 15:58:35 +02:00
- name: Copy firewalld public zone file
roles/common: Bump version checks to Debian 9
2019-10-26 16:37:27 +02:00
when: ansible_distribution_major_version is version_compare('9', '>=')
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html
2018-04-26 15:58:35 +02:00
template: src=public.xml.j2 dest=/etc/firewalld/zones/public.xml owner=root mode=0600
roles/common: Add firewalld support Needed in Ubuntu 15.04 where iptables-persistent is going away. I have added translations of the current IPv4 and IPv6 iptables rules. Signed-off-by: Alan Orth <alan.orth@gmail.com>
2015-06-07 11:42:03 +02:00
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html
2018-04-26 15:58:35 +02:00
- name: Format public.xml firewalld zone file
roles/common: Bump version checks to Debian 9
2019-10-26 16:37:27 +02:00
when: ansible_distribution_major_version is version_compare('9', '>=')
roles/common: Use blocks to tag children of dynamic tasks When using dynamic includes, child tasks do not inherit tags from their parents. You must tag the parent and each child task separately, or use a block to group children and then apply a tag to a block. See: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html
2018-04-26 15:58:35 +02:00
command: tidy -xml -iq -m -w 0 /etc/firewalld/zones/public.xml
notify:
roles/common: Restart firewalld instead of reload I'm having problems with reload hanging on Debian 10 so I will just revert to the older behavior of restarting.
2019-10-05 11:29:30 +02:00
- restart firewalld
roles/common: Add ipsets of abusive IPs to firewalld This uses the ipsets feature of the Linux kernel to create lists of IPs (though could be MACs, IP:port, etc) that we can block via the existing firewalld zone we are already using. In my testing it works on CentOS 7, Ubuntu 16.04, and Ubuntu 18.04. The list of abusive IPs currently comes from HPC's systemd journal, where I filtered for hosts that had attempted and failed to log in over 100 times. The list is formatted with tidy, for example: $ tidy -xml -iq -m -w 0 roles/common/files/abusers-ipv4.xml See: https://firewalld.org/2015/12/ipset-support
2019-10-05 11:28:30 +02:00
- name: Copy ipsets of abusive IPs
roles/common: Bump version checks to Debian 9
2019-10-26 16:37:27 +02:00
when: ansible_distribution_major_version is version_compare('9', '>=')
roles/common: Add ipsets of abusive IPs to firewalld This uses the ipsets feature of the Linux kernel to create lists of IPs (though could be MACs, IP:port, etc) that we can block via the existing firewalld zone we are already using. In my testing it works on CentOS 7, Ubuntu 16.04, and Ubuntu 18.04. The list of abusive IPs currently comes from HPC's systemd journal, where I filtered for hosts that had attempted and failed to log in over 100 times. The list is formatted with tidy, for example: $ tidy -xml -iq -m -w 0 roles/common/files/abusers-ipv4.xml See: https://firewalld.org/2015/12/ipset-support
2019-10-05 11:28:30 +02:00
copy: src={{ item }} dest=/etc/firewalld/ipsets/{{ item }} owner=root group=root mode=0600
loop:
- abusers-ipv4.xml
- abusers-ipv6.xml
notify:
roles/common: Restart firewalld instead of reload I'm having problems with reload hanging on Debian 10 so I will just revert to the older behavior of restarting.
2019-10-05 11:29:30 +02:00
- restart firewalld
roles/common: Add support for fail2ban This is active banning of IPs that are brute forcing login attempts to SSH, versus the passive banning of 10,000 abusive IPs from the abuseipdb.com blacklist. For now I am banning IPs that fail to log in successfully more than twelve times in a one-hour period, but these settings might change, and I can override them at the group and host level if needed. Currently this works for CentOS 7, Ubuntu 16.04, and Ubuntu 18.04, with minor differences in the systemd configuration due to older versions on some distributions. You can see the status of the jail like this: # fail2ban-client status sshd Status for the jail: sshd |- Filter | |- Currently failed: 0 | |- Total failed: 0 | `- Journal matches: _SYSTEMD_UNIT=sshd.service + _COMM=sshd `- Actions |- Currently banned: 1 |- Total banned: 1 `- Banned IP list: 106.13.112.20 You can unban IPs like this: # fail2ban-client set sshd unbanip 106.13.112.20
2019-10-26 16:36:07 +02:00
- include_tasks: fail2ban.yml
when: ansible_distribution_major_version is version_compare('9', '>=')
roles/common: Use dynamic include_tasks for firewall Use dynamic includes instead of static imports when you are running tasks conditionally or using variable interpolation. The down side is that you need to then tag the parent task as well as all child tasks, as tags only apply to children of statically imported tasks.
2018-04-25 17:58:31 +02:00
tags: firewall
roles/common: Add missing vim modelines
2018-04-25 17:55:22 +02:00
# vim: set sw=2 ts=2:
Reference in New Issue Copy Permalink