Open meh opened 4 years ago
Wait, I'm a dummy, digged a little deeper and iptables-nftables-compat
is just iptables
, and it's the same for iptables-nft
in Arch, is the issue just the way the check is done in the nftables
service?
I'm still waiting for this to get merged https://github.com/NixOS/nixpkgs/pull/81172 I guess this will fix nftables+docker for me and might be related to your issue
I marked this as stale due to inactivity. → More info
Since iptables and nftables work completely fine together, I'm seriously questioning the value of having the ip_tables
check in nixpkgs/nixos/modules/services/networking/nftables.nix
at all.
Simply removing the checkScript
portion of the service would obviously solve this problem, as well as any future "bad piece of software decided to load ip_tables
and now I can't update my firewall" issues.
With the switch to iptables-nft
, the nftables
NixOS module should probably be revisited. I opened https://github.com/NixOS/nixpkgs/issues/161428 as a proposal.
Describe the bug
libvirtd
seems to be able to bring up iptables and load theip_tables
module even when it's in the blacklist, this seems to be similar to what was happening in #24318, and thelibvirtd
module is in fact includingpkgs.iptables
instead ofconfig.networking.firewall.package
which I guess would make it work when usingpkgs.iptables-nftables-compat
.To Reproduce Steps to reproduce the behavior:
nftables
.nixos-rebuild switch
libvirtd
.nixos-rebuild switch
Expected behavior For
libvirtd
to use the right firewall package and not load theip_tables
module.Additional context I've used
libvirtd
before withiptables-nft
on Arch, and it was working properly.Notify maintainers @globin @fpletz
Metadata
Maintainer information: