default-in is also checking for conntrack status, so we should put this
there as well. Other than that consider this:
Tested-by: Stefan Hanreich <s.hanre...@proxmox.com>
Reviewed-by: Stefan Hanreich <s.hanre...@proxmox.com>
On 2/20/25 16:14, Hannes Laimer wrote:
> ... on the guest table. There is no reason to not repect that option
> on those two chains. These two were missed in the referenced commit.
>
> Fixes: 64dc344b ("firewall: apply `nt_conntrack_allow_invalid` option to
> guest table")
> Signed-off-by: Hannes Laimer <h.lai...@proxmox.com>
> ---
> proxmox-firewall/resources/proxmox-firewall.nft | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/proxmox-firewall/resources/proxmox-firewall.nft
> b/proxmox-firewall/resources/proxmox-firewall.nft
> index 2dd7c48..30f7b4f 100644
> --- a/proxmox-firewall/resources/proxmox-firewall.nft
> +++ b/proxmox-firewall/resources/proxmox-firewall.nft
> @@ -356,7 +356,7 @@ table bridge proxmox-firewall-guests {
> }
>
> chain pre-vm-out {
> - meta protocol != arp ct state vmap { established : accept, related :
> accept, invalid : drop }
> + meta protocol != arp ct state vmap { established : accept, related :
> accept, invalid : jump invalid-conntrack }
> }
>
> chain vm-out {
> @@ -384,7 +384,7 @@ table bridge proxmox-firewall-guests {
>
> chain before-bridge {
> meta protocol arp accept
> - meta protocol != arp ct state vmap { established : accept, related :
> accept, invalid : drop }
> + meta protocol != arp ct state vmap { established : accept, related :
> accept, invalid : jump invalid-conntrack }
> }
>
> chain forward {
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
