Tranquil IT Forum

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?

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

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

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.