Networking and Firewall Guide¶

This page summarizes network boundaries for IPCom from an IT operations perspective.

1. Traffic directions¶

• Inbound to IPCom: device traffic reaches configured receiver listeners (TCP/UDP/COM/modem paths).
• Outbound from IPCom: events and status traffic are sent to CMS/automation outputs.

2. Firewall planning¶

• Allow inbound receiver listener ports only from trusted device/source networks.
• Allow outbound traffic only to approved CMS/automation destination IPs and ports.
• Keep management UI access limited to admin networks, jump hosts, or VPN.
• Review NAT and port-forwarding rules before changing listener ports in Receivers.

3. IP allowlist notes¶

• IP Whitelist applies to the output types where IPCom listens for an incoming connection: JSON Server and TCP Server. Set it per output in the Outputs tab.
• It filters by source: only the addresses you list may connect to that listener. It does not restrict where IPCom sends outgoing traffic, so outbound output types are unaffected by it.

4. Change checklist¶

1. Apply firewall and NAT changes before modifying production receiver/output settings.
2. Validate connectivity with controlled test events.
3. Monitor Status buffers and Logs for rejects or connection failures.
4. Keep a rollback rule set for quick recovery.