Sure, like I said, it can be done with iptables. But: 1. Why do we have firewalld then? It seems to me that such a trivial thing should be configurable with firewalld.
2. The command that I tried firewall-cmd --permanent --add-rich-rule="rule family='ipv4' protocol value="tcp" destination address='aa.bb.0.0/16' reject" didn't put anything in iptables, i.e. iptables --list shows no rules. On the other hand, I do have this reject rule in /etc/firewalld/zones/ FedoraWorkstation.xml. Under the hood, by default, firewalld uses the newer nftables instead of iptables. I don't know how these two interact, if anything maybe we should do this in nftables. On Sun, 18 Jun 2023 15:26:16 -0700, Mike Wright wrote: > On 6/18/23 11:15, Amadeus WM via users wrote: >> Say I want to drop/reject outgoing connections to a particular >> destination address (for parental control). How would I do this with >> firewalld? > > How about bypassing firewalld and using iptables directly to add a rule > to the kernel? > > iptables -A OUTPUT -d address-to-ignore/xx -j DROP > > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org To unsubscribe send > an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List > Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List > Archives: > https://lists.fedoraproject.org/archives/list/ users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
