No magic limitation on socket size
|Reported by:||samuli||Owned by:|
|Component:||Networking||Version:||2.1.0 / 2.1.1|
|Severity:||Not set (if unsure, select this one)||Keywords:|
i think this patch https://community.openvpn.net/openvpn/changeset/e2e10f8d7a4d9477a8e35d10df5f54885fe3c092 is a problem.
If we want to do a vpn transfer at 100mb/s or more, we need a big socket size. An userland process lag of 2 seconds cause a buffering in kernel socket of at least 200Mb (25MB).
So we need a value in configuration to set the socket size. Cool we have one! But a *magic* value limit the socket size to 1Mo. First issue, if this value is bad : no error / warning message is printed.
2 choices is binding us, change the magic value in socket.h to a biggest value. Equally magical. I think it's the system job to know the max hardware driven max socket size and not to openvpn program. kernel have max value and default value so not need to be checked.
A last point, this is not theorical request, this come from a use case trouble.
So i think we need to rollback this patch.