> -----Original Message-----
> From: Alexandre DERUMIER [mailto:[email protected]]
> Sent: Mittwoch, 19. März 2014 06:33
> To: Dietmar Maurer
> Cc: [email protected]
> Subject: Re: [pve-devel] [PATCH] add ips feature v3
>
> I'll send a new patch today, I found some other missing accept
OK
I am still a bit unhappy with that PVEFW-Accept chain.
>this create a new chain PVEFW-Accept
>
>-A PVEFW-FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j PVEFW-Accept
All those checks are unnecessary, because we have already check it in tap-IN
chain? And the PVEFW-Accept
can grow really large because all interfaces from all VMs are added to a single
chain (not per bridge)?
>-A PVEFW-Accept -m physdev --physdev-out tapxxx --physdev-is-bridged -j
>NFQUEUE --queue-num 0 --queue-bypass
>-A PVEFW-Accept -m physdev --physdev-out tapxxx --physdev-is-bridged -j
>NFQUEUE --queue-num 0 --queue-bypass
>-A PVEFW-Accept -j ACCEPT
Then I saw that you also jump to PVEFW-Accept for OUT traffic:
ruleset_create_chain($ruleset, "$bridge-IN");
ruleset_addrule($ruleset, "$bridge-FW", "-m physdev --physdev-is-out -j
$bridge-IN");
- ruleset_addrule($ruleset, "$bridge-FW", "-m mark --mark 1 -j ACCEPT");
# AFAIK this is for direction OUT
+ ruleset_addrule($ruleset, "$bridge-FW", "-m mark --mark 1 -j
PVEFW-Accept");
why?
_______________________________________________
pve-devel mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
