Hi,

On 16/08/2019 13:49, David Sommerseth wrote:
> On 15/08/2019 17:53, Gert Doering wrote:
>> For reasons historically unknown, OpenVPN sets the listen() backlog
>> queue to "1", which signals the kernel "while there is one TCP connect
>> waiting for OpenVPN to handle it, refuse all others" - which, on
>> restarting a busy TCP server, will create connection issues.
>>
>> The exact "best" value of the backlog queue is subject of discussion,
>> but for a server that is not extremely busy with many connections
>> coming in in parallel, there is no real difference between "10" or "500",
>> as long as it's "more than 1".
>>
>> Found and debugged by "mjo" in Trac.
>>
>> Trac: #1208
>>
>> Signed-off-by: Gert Doering <g...@greenie.muc.de>
> 
> Acked-By: David Sommerseth <dav...@openvpn.net>
> 
> I agree with Antonio, and we should make it somewhat easier to modify.

I disagree with you on this point :D This is not something we expect
people to play with. This is only a value that a developer with
networking knowledge is expected to find and tweak. Hence my suggestion
to make it a define in some header main header file.

>  I'm
> not sure if there's value in having it as a runtime option, like
> --socket-backlog (or something like that), or as a value you can pass to
> ./configure at compile time.
> 

Like above: yet another config option that the average joe can mess up
and come up with unknown problems nobody will understand? nonono ;)

Cheers,

> 
> 
> 
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
> 

-- 
Antonio Quartulli

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to