OpenVPN

Let’s say you have an old dedicated server without AES-NI and you need 200 devices connected to it, but they only route traffic for a web server and a file server on your private network, and about 50% will be actively using the connection, and 50% will be idling, at any given time. As in the previous example this will of course vary somewhat as some users are working on other tasks and alternate this with retrieving files and data through the VPN tunnel. Let’s say you want to make sure each active users will have 10Mbps available, and let’s again assume they actually have that bandwidth on their Internet connection.

100 active users times 10Mbps is 1000Mbps or 1Gbps. Most systems nowadays have this by default, even servers that are several years old. 1000Mbps time 40MHz is about 40000MHz or 40GHz. Older servers with a dual octa-core setup with 2.5GHz will be able to get you to those requirements. With 200 connected devices in this example you would need about 2GB of memory, a fairly low amount.

Knowledge

apt install telnet
telnet localhost 1194
telnet nas0.dev.shahed.biz 80
telnet nas0.dev.shahed.biz 1194

apt purge openmediavault-openvpn
rm -rf /etc/openvpn/

sysctl -w net.ipv4.tcp_window_scaling=0

References

OpenVPN Access Server System Requirements Prevent SSH freezes over an OpenVPN Client Config an OpenVPN Server on Ubuntu 18.04 Config an OpenVPN Server on Ubuntu 16.04 OpenVPN Connect Client On Windows OpenVPN not Listening on Port 1194 OpenVPN Pi Setup not Listening OpenVPN How To OpenVPN PiVPN