Firewalld - Revision history

Ardika Sulistija at 18:51, 12 May 2025

2025-05-12T18:51:46Z

← Older revision		Revision as of 18:51, 12 May 2025
Line 37:		Line 37:
	Then confirmed that I was able to connect to the server on port 80 via a web browser.		Then confirmed that I was able to connect to the server on port 80 via a web browser.

	====How to allow rule ports for a specific subnet====		====How to allow rule ports for a specific subnet using Rich-rules====
	----		----

Ardika Sulistija at 18:50, 12 May 2025

2025-05-12T18:50:08Z

← Older revision		Revision as of 18:50, 12 May 2025
Line 12:		Line 12:

	If it's active (running), firewalld is enabled.		If it's active (running), firewalld is enabled.


	====List active firewall rules====		====List active firewall rules====
Line 35:		Line 36:

	Then confirmed that I was able to connect to the server on port 80 via a web browser.		Then confirmed that I was able to connect to the server on port 80 via a web browser.

			====How to allow rule ports for a specific subnet====
			----

			$ sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=<IP address>/16 port protocol=udp port=123-456 accept'
			$ sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=<IP address>/16 port protocol=udp port=123 accept'
			$ dzdo firewall-cmd --reload

Ardika Sulistija at 23:37, 25 February 2025

2025-02-25T23:37:41Z

← Older revision		Revision as of 23:37, 25 February 2025
Line 4:		Line 4:

	<b>firewalld</b> - A wrapper for iptables to allow easier management of iptables rules. Is <b>not</b> an iptables replacement. It's a firewall service <u>daemon</u> that provides a dynamic customizable host-based firewall with a D-Bus interface. It enables creating, changing, and deleting the rules without the necessity to restart the firewall daemon each time the rules are changed.		<b>firewalld</b> - A wrapper for iptables to allow easier management of iptables rules. Is <b>not</b> an iptables replacement. It's a firewall service <u>daemon</u> that provides a dynamic customizable host-based firewall with a D-Bus interface. It enables creating, changing, and deleting the rules without the necessity to restart the firewall daemon each time the rules are changed.


			====Check if firewalld is running====
			----
			Run:
			sudo systemctl status firewalld

			If it's active (running), firewalld is enabled.

			====List active firewall rules====
			----
			sudo firewall-cmd --list-all

Ardika Sulistija: Created page with "https://www.tecmint.com/start-stop-disable-enable-firewalld-iptables-firewall/ Good article: https://www.linode.com/docs/guides/introduction-to-firewalld-on-centos/ firewalld - A wrapper for iptables to allow easier management of iptables rules. Is not an iptables replacement. It's a firewall service daemon that provides a dynamic customizable host-based firewall with a D-Bus interface. It enables creating, changing, and deleting the rules without..."

2024-08-27T00:15:43Z

Created page with "https://www.tecmint.com/start-stop-disable-enable-firewalld-iptables-firewall/ Good article: https://www.linode.com/docs/guides/introduction-to-firewalld-on-centos/ firewalld - A wrapper for iptables to allow easier management of iptables rules. Is not an iptables replacement. It's a firewall service daemon that provides a dynamic customizable host-based firewall with a D-Bus interface. It enables creating, changing, and deleting the rules without..."

New page

https://www.tecmint.com/start-stop-disable-enable-firewalld-iptables-firewall/

Good article: https://www.linode.com/docs/guides/introduction-to-firewalld-on-centos/

firewalld - A wrapper for iptables to allow easier management of iptables rules. Is not an iptables replacement. It's a firewall service daemon that provides a dynamic customizable host-based firewall with a D-Bus interface. It enables creating, changing, and deleting the rules without the necessity to restart the firewall daemon each time the rules are changed.

====How to Allow HTTP connectivity in firewall (RHEL8)====
----

I was configuring apache (httpd) on a RHEL8 server. I had apache running and listening on port 80 and I confirmed that DNS was resolving the domain successfully. However, when I attempted to connect to the server on port 80 (using curl -IvkL) I was getting "No route to host":

curl: (7) Failed to connect to 123.abc.com port 80: No route to host

I checked iptables -L but did not see any iptables rules.

Then I found [https://www.linode.com/docs/guides/introduction-to-firewalld-on-centos/ this article] and found that I needed to allow http in the firewall rules.

sudo firewall-cmd --zone=public --add-service=http --permanent
sudo firewall-cmd --zone=public --reload
sudo firewall-cmd --zone=public --list-all

Then confirmed that I was able to connect to the server on port 80 via a web browser.

====How to check Firewall configurations for a specific Zone====
----
$ sudo firewall-cmd --zone=public --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: eth0
sources:
services: cockpit dhcpv6-client http ssh
ports:
protocols:
forward: no
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules: