Applies to: GP-Probe TGE2, GP-Probe DIN L1
What protocols does the GP-Probe use to communicate with GP-Cloud?
Devices use only standard Internet protocols for outbound connectivity:
Purpose | Protocol | Port | Direction | Notes |
---|---|---|---|---|
DNS resolution | UDP | 53 | Outbound | Resolve GP-Cloud hostname to IP. |
Secure data exchange with GP-Cloud | HTTPS (TCP) | 443 | Outbound | Telemetry, events, status, firmware checks/updates. |
Custom GP-Cloud endpoint?
If you run an on-prem or non-standard instance that listens on a custom TCP port, open that port for outbound traffic as well.
Which ports are used by the built-in Web Configuration Panel?
Local device management is performed via the integrated web UI and auxiliary services:
Service | Protocol | Port(s) | Applies to | Notes |
---|---|---|---|---|
HTTP Web UI | TCP (HTTP) | 80, 8080, 8081, 8082, 8083, 8085 | TGE2, DIN L1 | Used for local configuration and charts. |
Events interface | TCP | 8084 | DIN L1 | Internal event channel used by the DIN L1 web panel. |
WebSocket stream (RAW/processed data) | TCP (WS) | 8083 | TGE2, DIN L1 | Optional. Used by STREAM feature for data capture/ingest. |
Security tip: Expose these management ports only to your trusted LAN or VPN. Do not open them to the public Internet.
Does the GP-Probe support SNMP monitoring?
Yes, SNMP can be enabled optionally.
Protocol | Port (default) | Direction | Notes |
---|---|---|---|
SNMP | UDP 161 | Inbound (from NMS) | Port is configurable in device settings. |
Quick checklist for IT / firewall teams
Function | Protocol | Port | Direction | Mandatory? |
---|---|---|---|---|
DNS | UDP | 53 | Outbound | Yes |
GP-Cloud connectivity | HTTPS (TCP) | 443 | Outbound | Yes |
Local Web UI | HTTP (TCP) | 80, 8080–8085 | Inbound (LAN) | Optional (for local admin) |
SNMP (if enabled) | UDP | 161 | Inbound (LAN) | Optional |