I've been testing out the newer nftables-based firewall, and outside of the (very annoying) syntax changes for iplists/aliases, it seems to be working well.
However, I noticed an issue when configuring a VM that has three network interfaces. Only two of the three interfaces have the firewall box checked, yet the third "unfirewalled" interface seems to still be getting firewall rules applied to it. I cannot connect to services running on that interface until I create a firewall rule allowing them through.
For now, I've created allow-all firewall rules for interfaces which are not meant to be firewalled, but is this meant to be intended behavior, or is this a known issue?
Thanks
However, I noticed an issue when configuring a VM that has three network interfaces. Only two of the three interfaces have the firewall box checked, yet the third "unfirewalled" interface seems to still be getting firewall rules applied to it. I cannot connect to services running on that interface until I create a firewall rule allowing them through.
For now, I've created allow-all firewall rules for interfaces which are not meant to be firewalled, but is this meant to be intended behavior, or is this a known issue?
Thanks
