Hi,
I'm about to do my monthly rebuild of my packages. Usually, most of our users are in our offices and use local repositories, but this time they're all working remotely. The download will therefore go through our internet connections via VPN. I'd like to avoid WAPT causing a high load on our internet/VPN connection, and I was wondering if it's possible to limit the transfer speed when downloading WAPT package updates?
Speed 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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
there is no bandwidth limitation at the agent level.
Besides, where should the limitation be set and what should it be?
If you want to set a limit on the server, here are some suggestions:
Linux:
https://doc.ubuntu-fr.org/qos
You can also configure nginx directly: (I've never tried it)
https://docs.nginx.com/nginx/admin-guid ... limit_rate
there is no bandwidth limitation at the agent level.
Besides, where should the limitation be set and what should it be?
If you want to set a limit on the server, here are some suggestions:
Linux:
https://doc.ubuntu-fr.org/qos
You can also configure nginx directly: (I've never tried it)
https://docs.nginx.com/nginx/admin-guid ... limit_rate
Hello,
You can also host a secondary repository with a hosting provider and point your agents to that repository if your organization allows split tunneling with your VPN. The primary repository must remain accessible via VPN for inventory updates, unless you also place it in the DMZ and enable client authentication via certificate.
Otherwise, as Simon suggests, this will need to be done at the router/firewall or nginx level.
Vincent
You can also host a secondary repository with a hosting provider and point your agents to that repository if your organization allows split tunneling with your VPN. The primary repository must remain accessible via VPN for inventory updates, unless you also place it in the DMZ and enable client authentication via certificate.
Otherwise, as Simon suggests, this will need to be done at the router/firewall or nginx level.
Vincent
Vincent CARDON
Tranquil IT
Tranquil IT
I would indeed have the option of hosting a secondary repository on a server external to our infrastructure. How can I restrict access to the packages to company PCs? A WAPT package can contain license keys, for example, and I wouldn't want an unauthorized person to be able to access them.
Alternatively, I have a secondary repository hosted by Apache on one of my sites, and I was able to limit the total bandwidth for the Apache virtual host using mod_bw. I need to figure out how to do this with Nginx for the primary repository.
Alternatively, I have a secondary repository hosted by Apache on one of my sites, and I was able to limit the total bandwidth for the Apache virtual host using mod_bw. I need to figure out how to do this with Nginx for the primary repository.
