2 ms·
I don't think that's fair. Linux users misunderstand nftables/iptables and UFW pretends to have complete control when it really doesn't. It's annoying, but the
by jeroenhd 3y ago
I don't think that's fair. Linux users misunderstand nftables/iptables and UFW pretends to have complete control when it really doesn't.
It's annoying, but the fault lies squarely with the lack of reporting of other chains in UFW.
- IshKebab 3y agoIf everyone is misunderstanding how something works it's because it doesn't work the right way. Clearly people want firewall rules that take priority over everything else.
- jeroenhd 3y agoI agree, and tools that try to make something complex (nftables) simple and easy to use (UFW, Firewalld) should make that possible. Different lists are a powerful nftables feature that is used in many system services and applications for things like routing and specialized forwarding. You can't just disable that without breaking tons of software. Instead, tools like UFW should make it clear which ports are or aren't open and what firewall rules actually apply to the current system. They exist to save users from nftables and eBPF programming, and they should work as advertised. Ufw advertises itself with "Ufw stands for Uncomplicated Firewall, and is program for managing a netfilter firewall" not "Ufw stands for Uncomplicated Firewall, which lets you add some firewall rules but doesn't manage all of them so you need to be extra careful if you use it."
- nextaccountic 3y agoThe real problem is that iptables rules aren't composable. In this thread alone there are several tools that add iptables rules (kubernetes, docker, ufw) and they are just dumped without regards to each other. This could be solved by more tooling.
- jeroenhd 3y agoI disagree that we need more tooling. We need better tooling. Docker and Kubernetes adding network filters makes total sense, they're useless without forwarding packets between devices. UFW, on the other hand, pretends to make firewalls simple and easy to use when they're really not. I'm not expecting UFW to start managing Docker's/K8s'/libvirtd's firewall rules, I'm just expecting them to add a section of "ports opened by other applications" that show the open ports that UFW can't control.