In CentOS 7 environments without cPanel\/WHM, Firewalld is the default firewall system. It is an improvement over the older Iptables, offering a more user-friendly interface with easier-to-understand commands.<\/p>\n
Firewalld organises rules in layers, making it easier for advanced administrators to manage traffic with fine-tuned configurations. While we won\u2019t dive into the more complex features, we will cover the basics of managing Firewalld.<\/p>\n
Follow the steps:<\/strong><\/p>\n By default, this service should be running unless configured otherwise.<\/li>\n<\/ol>\n<\/li>\n Use \u201ccomplete-reload\u201d carefully as it disconnects active sessions temporarily, though it keeps state information such as temporary rules intact. If you have added permanent rules, you will need to reload the firewall so they can take effect.<\/li>\n<\/ol>\n<\/li>\n If you want the rule to persist after a restart of Firewalld or the server, use the –permanent option. The debug levels are: This will help you understand where issues might be occurring with your firewall configuration.<\/li>\n<\/ol>\n And that is it! We hope you found this article helpful. If you have any questions or run into issues, don\u2019t hesitate to contact our support team.<\/p>\n","protected":false},"excerpt":{"rendered":" In CentOS 7 environments without cPanel\/WHM, Firewalld is the default firewall system. It is an improvement over the older Iptables, offering a more user-friendly interface with easier-to-understand commands. Firewalld organises…<\/p>\n\n
\n
systemctl start firewalld.service<\/pre>\n
\nTo check the status of Firewalld, you can use either of these commands:<\/p>\n\n
systemctl status firewalld.service<\/pre>\n<\/li>\n
firewalld-cmd \u2013state<\/pre>\n<\/li>\n<\/ol>\n<\/li>\n
\nWhen you add or change rules, Firewalld must be reloaded to apply them. There are two ways to reload the firewall:<\/p>\n\n
firewalld-cmd \u2013reload<\/pre>\n<\/li>\n
firewalld-cmd --complete-reload<\/pre>\n
\nTo open a port in the firewall, use the subsequent commands. You can apply these rules temporarily or permanently:<\/p>\n\n
firewall-cmd --zone=public --add-port=80\/tcp<\/pre>\n<\/li>\n
firewall-cmd --permanent --zone=public --add-port=80\/tcp<\/pre>\n
\nAlways reload the firewall after adding a permanent rule.<\/li>\n<\/ol>\n<\/li>\n
\nIf you are troubleshooting and need more insight into what\u2019s happening with your firewall, you can enable debugging in the Firewalld configuration. The debugging level will control the verbosity of the logs.To enable debugging, edit the \u201c\/etc\/sysconfig\/firewalld\u201d file and add the following to the \u201cFIREWALLD_ARGS\u201d line:<\/p>\n--debug=[level]<\/pre>\n
\n1: Loading config files, D-Bus method calls
\n2: Backend calls, D-Bus introspection, and access checks
\n3: Rules added by backends
\n4: Transaction steps
\n5-9: Unused (no effect)
\n10: XML data introspection<\/p>\n