From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Subject: [RFC] IPVS: secure_tcp does provide alternate state timeouts Date: Thu, 29 Sep 2011 16:25:11 +0900 Message-ID: <1317281111-23985-1-git-send-email-horms@verge.net.au> Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, Simon Horman To: Julian Anastasov Return-path: Sender: lvs-devel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org * Also reword the test to make it read more easily (to me) Signed-off-by: Simon Horman --- Julian, I don't see that IPVS currently implements alternate timeouts for secure_tcp. Am I missing something? --- Documentation/networking/ipvs-sysctl.txt | 10 ++++------ 1 files changed, 4 insertions(+), 6 deletions(-) diff --git a/Documentation/networking/ipvs-sysctl.txt b/Documentation/networking/ipvs-sysctl.txt index 1dcdd49..13610e3 100644 --- a/Documentation/networking/ipvs-sysctl.txt +++ b/Documentation/networking/ipvs-sysctl.txt @@ -140,13 +140,11 @@ nat_icmp_send - BOOLEAN secure_tcp - INTEGER 0 - disabled (default) - The secure_tcp defense is to use a more complicated state - transition table and some possible short timeouts of each - state. In the VS/NAT, it delays the entering the ESTABLISHED - until the real server starts to send data and ACK packet - (after 3-way handshake). + The secure_tcp defense is to use a more complicated TCP state + transition table. For VS/NAT, it also delays entering the + TCP ESTABLISHED state until the three way handshake is completed. - The value definition is the same as that of drop_entry or + The value definition is the same as that of drop_entry and drop_packet. sync_threshold - INTEGER -- 1.7.5.4