vast acorn
If the state of documentation is not up to date it explains my troubles and I am fine.
My libvirt machine NAT stopped working due to switching to nftables.
The archwiki states I need to allow access to DHCP/DNS via NAT in /etc/nftables.conf.
This doesn't worked.
Found an old forum entry (latest entry 2024) stating I need to define firewall_backend=iptables instead of defaulting to notables because they( adonesp stated ) use iptables-nft.
So my question what is correct in 2026?
The config change from 2024 worked. But I am curious about the archwiki entry about nftables.
pearl trellis
The config change from 2024 worked. But I am curious about the archwiki entry ab...
Correct modern default: firewalld (nft backend) or direct nftables.
But in practice: many setups still rely on iptables compatibility layer (iptables-nft) inside libvirt. So your forum fix (firewall_backend=iptables) working is not surprising at all.
vast acorn
Mhm but I was not able to get NAT to outside DNS working with direct nftables described in the wiki.
Or is this an issue with VirtManager?
pearl trellis
Mhm but I was not able to get NAT to outside DNS working with direct nftables de...
Did you configure libvirt?
vast acorn
Did you configure `libvirt`?
I configured it just with firewall_backend=iptables now before not