Problems with Wapt communication

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Locked
Angel Herrera
Messages: 1
Registration: January 11, 2019 - 02:26

January 12, 2019 - 00:32

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
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

January 14, 2019 - 6:39 PM

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.

Code: Select all

repo_url=http://waptrepo1.mydomain.local/wapt
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked