From d238e4bd0026a80b8d421b371abe0b1d3ebb2547 Mon Sep 17 00:00:00 2001 From: Fabian Mauchle Date: Tue, 16 May 2017 17:59:44 +0200 Subject: [PATCH] add documentation for tcpKeepalive --- radsecproxy.conf.5.xml | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/radsecproxy.conf.5.xml b/radsecproxy.conf.5.xml index b5f71b6..4f706b8 100644 --- a/radsecproxy.conf.5.xml +++ b/radsecproxy.conf.5.xml @@ -510,6 +510,7 @@ blocktype name { certificateNameCheck, matchCertificateAttribute, duplicateInterval, AddTTL, + tcpKeepalive fticksVISCOUNTRY, fticksVISINST, rewrite, rewriteIn, rewriteOut, and @@ -587,6 +588,11 @@ blocktype name { that for details. Any value configured here overrides the basic one when sending messages to this client. + + The tcpKeepalive option enables TCP keepalives. If + keepalives are not answered withing 30s the connections is considered + lost. + The fticksVISCOUNTRY option configures clients eligible to F-Ticks logging as defined by the @@ -682,7 +688,8 @@ blocktype name { type, secret, tls, certificateNameCheck, matchCertificateAttribute, - AddTTL, rewrite, + AddTTL, tcpKeepalive, + rewrite, rewriteIn, rewriteOut, statusServer, retryCount, dynamicLookupCommand and @@ -704,7 +711,8 @@ blocktype name { type, secret, tls, certificateNameCheck, matchCertificateAttribute, - AddTTL, rewrite, + AddTTL, tcpKeepalive, + rewrite, rewriteIn and rewriteOut are just as specified for the client block above, except that defaultServer (and not