References: <1467430368-25437-1-git-send-email-selva.nair@...277...> <1467502488-31549-1-git-send-email-selva.nair@...277...> <11772d2a-4877-0ed0-2484-7ef66e059737@...1227...> From: Arne Schwabe Message-ID: Date: Mon, 4 Jul 2016 23:01:06 +0200 MIME-Version: 1.0 In-Reply-To: Subject: Re: [Openvpn-devel] [PATCH v2] Exponentially back off on repeated connect retries List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit To: Selva Nair Cc: "openvpn-devel@lists.sourceforge.net" > Or do you have tcp-client in mind? In case of tcp-client, before this > patch, "--connect-retry 0" will hammer the server with repeated > retries. That will be avoided as max sec defaults to 300 sec, unless > the user specifies "--connect-retry 0 0". Shall we require that the > second arg to connect-retry should be greater than some minimum, say, at > least 10 sec? No, the TCP-SERVER line there is for p2p mode but with tcp-server. In p2p mode with p2p the code will also execute that socket-restart code after the other side will disconnect. Arne