Forum GLPI-Project

larsen

Member

Registered: 2024-09-04

Posts: 7

GLPI Inventory - Deployment with P2P is scanning all networks

Testing software deployment using the P2P option. I then noticed that the agent scans every host in every available network:

[Tue Nov 12 17:38:41 2024][info] running task Deploy
[Tue Nov 12 17:38:41 2024][info] looking for a peer in the network
[Tue Nov 12 17:43:59 2024][error] [http client] internal response: 500 Can't connect to 192.168.56.89:62354 ...
[Tue Nov 12 17:44:00 2024][error] [http client] internal response: 500 Can't connect to 192.168.0.247:62354 ...
[Tue Nov 12 17:44:01 2024][error] [http client] internal response: 500 Can't connect to 192.168.188.178:62354 ...
[Tue Nov 12 17:44:02 2024][error] [http client] internal response: 500 Can't connect to 192.168.191.109:62354 ...

Is there a way to tell the agent to only scan a specific network for P2P transfers?

larsen

Member

Registered: 2024-09-04

Posts: 7

Re: GLPI Inventory - Deployment with P2P is scanning all networks

As Guillaume stated in github.com/glpi-project/glpi-agent/issues/804#issuecomment-2477602893

Sorry, no, there's actually no way to specify where network can or cannot be scanned for agent.
Agent P2P support is pretty old and should probably be upgraded to a better solution in the future.

Created a feature request: glpi.userecho.com/communities/1/topics/2418-only-scan-specific-networks-for-p2p-transfers

Last edited by larsen (2024-11-15 13:17:59)