linux-kernel - Re:Re: [PATCH] ipvs: add a sysctl switch to control ipvs to bypass OUTPUT chain or not

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <e1adaaad-49f-de31-1dff-183eee242dc@ssi.bg>
Date:   Thu, 25 Aug 2022 08:32:51 +0300 (EEST)
From:   Julian Anastasov <ja@....bg>
To:     "longguang.yue" <bigclouds@....com>
cc:     horms@...ge.net.au, kadlec@...filter.org, fw@...len.de,
        pablo@...filter.org, lvs-devel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re:Re: [PATCH] ipvs: add a sysctl switch to control ipvs to bypass
 OUTPUT chain or not


	Hello,

On Thu, 25 Aug 2022, longguang.yue wrote:

> I see. 
> I hope we could find a maintainable and decoupled way to keep ipvs high performance.
> especially for kubernetes environment, there are from dozens up to one hundred rules in OUTPUT chain.

	May be some rules can help the bunch of rules to
be applied only for first packet, not for every packet in
connection, such as:

iptables -t filter -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -t filter -A OUTPUT -m ipvs --ipvs -j ACCEPT

Regards

--
Julian Anastasov <ja@....bg>