Kemudian mari kita install iptables: yum install iptables-services. Cegah supaya firewalld dijalankan saat booting/startup CentOS 7: systemctl mask firewalld. Using iptables works just fine, but I have to switch it to firewalld due dev-env issues mentioned above. Sebenarnya juga bukan hal yang sulit, langkah paling pertama adalah mematikan firewalld: systemctl stop firewalld.

I'm using my webservers' subnet as source, or should I list each webserver's ip as source?Īlthough when I deploy the ansible configuration, it doesn't work at all. In this way, I have to manually add the rule #3 to each slave server (currently there are only 3 slave servers, but it's going to be way more at some point, thus, I'm planning on automatically deploying it through ansible).Īnd the ansible config that I've set looks like this: - name: Redis service My iptables looks like this: 1 iptables -N REDISĢ iptables -A REDIS -s 10.0.1.11 -j ACCEPT # Master serverģ iptables -A REDIS -s 10.0.1.10 -j ACCEPT # Slave 01/03Ĥ iptables -A REDIS -j LOG -log-prefix 'unauth-redis-access'ĥ iptables -A REDIS -j REJECT -reject-with icmp-port-unreachableĦ iptables -I INPUT -p tcp -dport 6379 -j REDIS IMHO, firewalld is more suited for workstations than for server environments. I'm setting up a new Redis cluster on my webservers, and currently I was adding some chain rules with the iptables settings, but now I'm switching to automatically deploying through ansible. With RHEL 7 / CentOS 7, firewalld was introduced to manage iptables.

Centos iptables