New answers tagged

2

Before you start firewalld service you should specify parameters via config files. I recommend to you to create file of rules for every service (GlusterFS, Pacemaker ...) and put in the file all ports that you need. For example (for pacemaker got from Configuring the iptables Firewall to Allow Cluster Components) /etc/firewalld/services/pacemaker.xml: <?...


0

Easy. Just add the option --permanent to all your rules, e.g. firewall-cmd --zone=trusted --add-port=1234/tcp --permanent This will register rules in the permanent configuration but won't apply them, until you run the command firewall-cmd --reload By the way, this is the recommended way to operate firewalld; if you don't use the --permanent option, ...


0

That's because on desktop machines, KDE Connect works as a server, and phone apps are connecting to it. This shouldn't really be an issue, as all the incoming connections are being authenticated first (you have to “accept pairing” from a device in order for it to be able to do anything with your PC), but if you want, you can disable the kdeconnectd service (...


Top 50 recent answers are included