Tranquil IT Forum

Good evening

- Installed version of WAPT server: 1.5.1.16
- Server OS: Debian GNU/Linux 9.3 (extension)


I am contacting you because I am having problems with communication from my nodes (Windows) to the repository servers.

Master VLAN Server 1
Repository Server 1 VLAN 2
Repository Server 2 VLAN 3
PC Nodes VLAN 2 and 3

Apparently, there is a blockage, but it's not that the port or service is blocked. Previously, a firewall allowed the connection, but when there was no firewall switching to the repository servers, it was redirected to the master server. The problem is that the master is outside the local network via MPLS and consumes a lot of bandwidth.

We have open services and ports:
HTTP,
SSH,
TCP port 8088,
and TCP port 22000 (Syncthing).

Do you have a solution to resolve this issue?

Thank you in advance.

Sincerely,

Angel Herrera

Hola Angel!

If you are more comfortable with English, we can also go the Yankee way My Spanish is a bit rusty...

Angel Herrera wrote: ↑Jan 12, 2019 - 00:32 Master VLAN Server 1
Server Repository VLAN 2
Server Repository VLAN 3
PC Nodes VLAN 2 and 3

So you have 3 debian 9.3 servers:
- waptserver on vlan1 in datacenter (debian 9.3)
- waptrepo1 on vlan2 on site1 (debian 9.3)
- waptrepo2 on vlan3 on site2 (debian 9.3)

And computers on physical site site1 and site2

Your issue is that computers are connecting to waptserver on vlan1 instead of connecting to their respective waptrepo1 or waptrepo2. Computers on vlan2 should connect to waptrepo1 and computers on vlan3 should connect to waptrepo2.

Currently there are two ways to help waptagent to download from the nearest repository: wapt-get.ini configuration or DNS configuration. The easiest thing to do is to explicitly configure the repository on your windows client using a configuration package like [1] setting the line repo_url.
You create two such packages and then apply them respectively to the computers on site1 and site2.

Cheers,

Denis

[1] https://store.wapt.fr/package_details?p ... 6_all.wapt