If your Azure issue is not addressed in this article, visit the Azure forums on MSDN and Stack Overflow. This article provides troubleshooting steps to help you resolve this problem. I will start testing next week and if there are people interested in the result and approach please give me a shout and I will share all the info, otherwise, I will not spam this thread any further.After you configure a site-to-site VPN connection between an on-premises network and an Azure virtual network, the VPN connection suddenly stops working and cannot be reconnected. At the moment we have a single host with 250 docker instances. The Amazon EC2 scripts from the OpenVPN wiki used for the past performance test look like a lot of work and were edited in 2012 so we have given up on getting them to work for us.įinally, the docker approach seems to work just fine. “For more than 100 simultaneous connections several parallel OpenVPN processes are used on the same client instance although the clients will fail to initialize properly, they should still stress the server in relatively realistic fashion.” Now the good news is that if you look to stress test the OpenVPN server according to the open VPN community this is still valid load, see extract from the OpenVPN wiki below:
On Client PC I have created 5/10/15/50/100 config files.Ĭ. On a single Client PC, I have created 5/10/15/50/100 TAP adaptersī.
While the simulated client connections will fail no matter if I am using 5 or 500.
So far the physical Client PCs are rock solid idling over the weekend.
Now the problem I am having is how to simulate reliably 500 Client connections using the preferably single physical device and keep them stable. O Clients will obtain the IP dynamically from the OpenVPN server
O Clients will use the same username password for the authentication O Clients would be started with a 10s delay between each new connection.