Overview
Share this page with the IT team before installation. It lists the network access C-Bridge needs. Port numbers can vary by release, so confirm them for the version you install.
Ports
| Port | Protocol | Direction | Purpose |
|---|---|---|---|
| 443 | TCP | Outbound | HTTPS to cloud services, updates and remote access |
| 3000 | TCP | Inbound, LAN only | Local web interface (HTTP); confirm for your release |
| 5000 | TCP | Inbound, LAN only | REST API and WebSocket |
| 47808 | UDP | Inbound and outbound, LAN only | BACnet/IP |
| 5353 | UDP | LAN | mDNS, only if using the cbridge-XXXX.local hostname |
Local ports should be reachable only by authorized clients on the LAN or VPN. The outbound cloud connection is separate.
Requirements
- Outbound internet: HTTPS on port 443 for OTA updates and cloud features. Without it the gateway keeps working locally but cloud features are unavailable.
- BMS access: if using BACnet, the BMS network must be able to reach the gateway on UDP 47808, on the same subnet or through routing.
- VLANs: the gateway can sit on a dedicated IoT VLAN. That VLAN needs internet access, access to the BMS network for BACnet, and mDNS forwarding if you want hostname resolution across VLANs. Otherwise use the IP address directly.
- Address: use a DHCP reservation or static IP.
- MAC filtering: if the network filters by MAC address, add the address from the device label.
Do not expose to the internet
Use the supported cloud access workflow or an IT-managed VPN. Do not forward the gateway's local HTTP, API, WebSocket or BACnet ports to the public internet.
Checklist for IT
- Outbound TCP 443 allowed
- Reserved or static IP assigned
- BMS can reach UDP 47808 (if using BACnet)
- Local ports not exposed publicly
- mDNS or direct IP access agreed