Tranquil IT Forum

Hello,

I have a WAPT Enterprise server (version 2.6.0.16714) installed on Debian (which we'll call wapt1).

To reduce network congestion and WADS/WAPT WUA requests, I decided to create secondary repositories for the WAPT WUA and WADS services:

- wapt2 will serve as the WAPT WUA repository

- wapt3 will serve as the WADS repository.

I therefore set up two separate machines and configured their synchronization so that they only retrieve the relevant directories.
Synchronization works correctly in the /opt/wapt/repository directory.

I then created repository rules stipulating that agents with an IP address belonging to the 192.168.0.0/16 network access:

- wapt2 for the wua folder

- wapt3 for the wads folder.

I also configured the use_repo_rules variable to true in the general agent configuration.

The secondary repositories contain the remote-repo-conf and remote-repo-nginx packages (as well as remote-repo-tftp).

However, when I check on a machine matching the defined rules, I don't see the secondary repositories, and it seems they aren't being used in their new role.

I've probably missed a step, but I can't figure out which one.

Can you help me, please?

Hello

, could you please provide details of the rule that was created?

The rule only mentions wua, so it won't be very visible on the client side.

You'll mainly see it if, for example, you delete wsusscn2.cab from a machine and the machine re-downloads the file.

You can also verify that downloads are indeed going through this repository by looking at the audit data:

host_metrics - peercache.

In the URLs, you'll see the source URL.

vincent.moisan wrote: ↑Feb 11, 2026 - 12:53 PM To relieve network congestion and WADS/WAPT WUA requests, I decided to create secondary repositories for the WAPT WUA and WADS services.

Actually, secondary repositories aren't for remote sites? Is this a secondary repository for your local network?

So, not very useful.

What I'd like is for the agents to no longer go through the main server for WaptWua and WADs.

So, a rule that redirects them to the correct repository depending on what's being requested.

The main server would then be used, in a way, only for application deployments.
Wapt2 would be used only for WaptWua, and Wapt3 for all OS deployments.

sfonteneau wrote: ↑Feb 11, 2026 - 1:56 PM

vincent.moisan wrote: ↑Feb 11, 2026 - 12:53 PM To relieve network congestion and WADS/WAPT WUA requests, I decided to create secondary repositories for the WAPT WUA and WADS services.

Actually, secondary repositories aren't for remote sites? Is this a secondary repository for your local network?

Yes. It's for a local network. It's an idea that was suggested by one of your trainers to relieve the load on the main server.

Secondary repositories are mainly used for remote sites behind a VPN (low bandwidth connection).

Often, the secondary repository hosts everything.

In your case, setting up a repository like this seems unnecessary.

Perhaps there was some misunderstanding?

@vincent.moisan,

do you have a Wapt server running on Windows? If so, it could be relevant because nginx on Windows isn't very performant. If the server is running Linux and is properly sized, it can serve 10,000 machines and easily saturate a 10Gb link...

Best regards,

Denis

dcardon wrote: ↑Feb 11, 2026 - 2:16 PM @vincent.moisan

Do you have a Wapt server running on Windows? If so, it could be relevant because nginx on Windows isn't very performant. If the server is running Linux and is properly sized, it can serve 10k machines and easily saturate a 10Gb link...

Best regards,

Denis

No, they are 3 Debian servers. The problem is network sizing. Our servers are VMs on KVM. So the congestion occurs first on the WAPT server, or if that's not the case, on the hypervisor or the network gateway.

We have 650 workstations downloading Windows 11 25H2 updates, each 12GB in size. However, this is clearly not feasible if we want to deploy operating systems, patch software vulnerabilities, and perform Windows Update applications (WUA), all on the same server. Therefore, the goal is to create secondary repositories to avoid overloading the network when all these tasks need to be performed simultaneously