If you are familiar with iptables, we recommend using iptables Guide To firewalld. For that reason, it is highly recommended that you not use this process. This means that future releases of the OS will be removing iptables. Verifying DISA STIG Compliance with OpenSCAP - Part 2Īs of Rocky Linux 9.0, iptables and all of the utilities associated with it, are deprecated. Host-based Intrustion Detection System (HIDS)īash - Conditional structures if and case I don’t know how to check if the boot sequence invokes iptables-restore…Īny thoughts on making iptables active with the saved rules after a reboot? Many thanks.Building and Installing Custom Linux KernelsĪutomatic Template Creation - Packer - Ansible - VMware vSphere I have been able to restore the rules manually using iptables-restore. The /etc/iptables.up.rules file contains the expected information (reflecting my rules). BUT… the Activate at boot is set to No after a reboot.įurthermore, if I reboot my server (say, by going to my VPS hosting control panel and clicking Reboot), when it comes back up, iptables -nL shows the default ACCEPT/ACCEPT/ACCEPT again. It looks as if that action took effect, too. I can click the Activate at boot button (after first clicking the Yes button).
I can make changes and click Apply Configuration and they go into effect. In the Webmin Linux Firewall page, I see my firewall rules as expected. I have a set of scripts that automatically update the iptables rules. I removed firewalld with sudo apt purge firewalld I want to use iptables (instead of firewalld). When my server restarts, all the firewall rules get lost and I go back to default (ACCEPT/ACCEPT/ACCEPT)
0 kommentar(er)
