Hello,
Our organization decided to use WAPT about 8 months ago for practical reasons related to remote work.
Our server was installed and hosted at the company headquarters.
We had no problems initially, but with an increasing number of remote workstations, we are experiencing significant slowdowns at headquarters due to our total bandwidth consumption. We have approximately 800 workstations in total, 70-75% of which are remote, and a fiber optic connection limited to 20 Mbps. During an update of a medium-sized application, such as Firefox, our bandwidth is completely used, causing malfunctions elsewhere.
We are quite limited in our options and decisions, and our organization cannot implement QoS on its own; the choice of WAPT was ours.
We are currently seeking appropriate solutions to mitigate these issues without compromising the effectiveness of WAPT. Currently, external hosting is not an option, and we are unsure of its functionality due to our internal security measures.
We tested Wondershaper to limit bandwidth on an interface, but this solution is far too restrictive, both for us at headquarters using the console and for updating 800 simultaneous workstations with a cap of 8 Mbps and download speeds between 15 and 30 KB/s, whether they are remote or local workstations.
Is there, and do you know of, a solution that would allow us to limit the number of simultaneous updates, such as a queue (e.g., 10 workstations at the same time)?
On the server side, I see options in the documentation such as "db_max_connections" or "max_client" that we haven't tried yet, but I'm afraid that options like "max_client" might block some of our workstations until other workstations are disconnected first…
I also considered whether it would be possible, with two network interfaces, to limit the bandwidth of our remote users based on their IP address, and use the other interface for local IPs, but I don't see if such filtering is possible on the WAPT server side…
If you have any answers, we'd be very grateful!
Thank you!
WAPT Community 1.8.2
CentOS 7
Bandwidth limitation and/or simultaneous customer limit
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Hello, in the Enterprise version, you have secondary repositories and the ability to fine-tune repository rules.
Therefore, if you allow split tunneling in your VPN, your upstream bandwidth saturation issue will be immediately, automatically, and permanently resolved with secondary repositories. If you don't allow split tunneling, then your best solution will be to increase your upstream bandwidth at headquarters.
In the Enterprise version, you will also receive a personalized explanation of why an internet-hosted repository is not considered sensitive property and an explanation of how to obscure the existence of your repository using client certificates.
Sincerely.
Therefore, if you allow split tunneling in your VPN, your upstream bandwidth saturation issue will be immediately, automatically, and permanently resolved with secondary repositories. If you don't allow split tunneling, then your best solution will be to increase your upstream bandwidth at headquarters.
In the Enterprise version, you will also receive a personalized explanation of why an internet-hosted repository is not considered sensitive property and an explanation of how to obscure the existence of your repository using client certificates.
Sincerely.
Vincent CARDON
Tranquil IT
Tranquil IT
