perfSONAR User Q&A and Other Discussion

[Bill Bradford <>]

Pete,

"firewall-cmd --zone=public --add-port=6556/tcp —permanent” adds the entry to the config file but doesn’t actually make it active.

"firewall-cmd --zone=public --add-port=6556/tcp" without the --permanent changes the running state but not the config file, so you need to do both. Or firewall-cmd --reload to pick up the change from the config.

Bill

On Jul 18, 2018, at 2:27 PM, Pete Siemsen <> wrote:

I'm trying to enable check_mk monitoring of my brand new perfsonar 4.0.2 system. In other words, I need to allow inbound connections to port 6556. My recipe for installing check_mk says to do this:

firewall-cmd --zone=public --add-port=6556/tcp --permanent

...which executed without error, but inbound access to port 6556 is still blocked.

Then I investigated and got confused. There's a firewalld process running, yet "iptables -L" shows some rules that apply to perfsonar.

So which firewall system is actually running: iptables or firewalld?

-- Pete

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user