Proxy Inventory with GLPI Agent for Segmented Networks

How to use the GLPI Agent proxy mode to inventory devices on isolated networks, DMZs and multi-site environments without direct access to the GLPI server.

In segmented network environments, not all devices can reach the GLPI server directly. The GLPI Agent proxy mode solves this with an intermediary agent.

When to use a proxy

  • Branch offices without a direct VPN to the data center
  • Isolated networks (DMZ, OT/ICS, laboratory)
  • Environments with restrictive firewalls (only HTTP/HTTPS egress)
  • Remote sites with unstable links

Architecture

[Network A Devices] → [GLPI Agent Proxy A] → [Internet/VPN] → [GLPI Server]
[Network B Devices] → [GLPI Agent Proxy B] → [Internet/VPN] → [GLPI Server]

Each network has a proxy agent. Devices on the network send their inventory to the local proxy. The proxy consolidates and sends it to GLPI.

Configuration

Proxy agent

glpi-agent --server https://glpi.suaempresa.com --httpd-trust 192.168.1.0/24 --listen

Local agents

glpi-agent --server http://proxy-local:62354

Best practices

  • Use HTTPS between the proxy and the GLPI server
  • Restrict --httpd-trust to the local network range
  • Configure redundancy: two proxies per critical network
  • Monitor the proxy with Zabbix or similar

Frequently Asked Questions

It is a mode in which a central agent collects inventories from other agents on the same network and forwards them to the GLPI server. Useful for networks without direct access to GLPI.

No. With the proxy, only the proxy agent needs access to GLPI. The other agents send their inventory to the local proxy.

Yes. The proxy collects locally and sends to GLPI via HTTPS (port 443). Only one firewall rule is required: proxy → GLPI server.

Need help?