Ah, obviously. #docker only gets along with #firewalld if the latter is using the iptables backend (not the higher performing nftables default).
The #iptables backend is depreciated and slated for removal.
And of course there's no error message if configured "incorrectly", just random breakage that one then gets to debug!
I hate computers. I wish I was good enough at something else.
Do you know how to set up a secure firewall for your network? Our 'firewalld' tutorial has had good reviews from users. It can walk a beginner through the process of setting up the default Rocky Linux firewall daemon. For users with some previous knowledge of older firewall technologies, the IpTables Guide helps translate that knowledge into the 'firewalld' setup. https://docs.rockylinux.org/guides/security/firewalld-beginners/#tutorialtuesday#firewalld#howto#linuxtips#documentation
Is it possible to install #gufw on #Fedora 38, because I’m REALLY tired of trying to figure out why #firewalld keeps ignoring anything I put into the “Trusted Zone?”
No, REALLY, I don’t want your help with firewalld. I’m never going to like it. I just want it gone.
Check the new "Donation list" to support your favourite free and open source software.
It includes all the #donation links with all the listed #tutorials and #services we provide.
PSA: if you run #Fedora 36 or later, check to see if your #firewalld service is running.
In a recent update they're still distributing a broken tcpcryptd.xml service definition file for which this over 4 year-old bug exists even though there are merge requests for fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1716080
What's really awful is it causes firewalld to not start and you won't notice unless you monitor its state. Ouch. 🤕
The more I am digging in to #linux, the more I am realizing I really need to take the time to grok #iptables. This way I'll understand what tools like #firewalld and #ufw are really doing.