Networking & Configuration

Overview

The Network Settings section in C-Bridge allows you to configure how the device connects to your local network and how it is accessed by users and external systems. Proper network configuration is essential for stable operation, reliable BACnet integration, and remote access capability.

Navigate to: Settings → Network

Connection Types

C-Bridge supports two connection methods:

Ethernet (Recommended)

• Provides the most stable and reliable connection for commercial deployments
• Automatically uses DHCP by default — no manual configuration needed in most cases
• Recommended for stable BACnet and API integrations
• Immune to Wi-Fi interference and signal fluctuations

Wi-Fi (Optional)

• Used when Ethernet is not practical or available
• Configured during initial setup (SoftAP mode) or from the Network Settings page
• Performance depends on signal strength and local RF interference
• Not recommended as the sole connection method for production BACnet integrations

IP Configuration

DHCP (Default)

C-Bridge uses DHCP by default — the device receives an IP address automatically from your network's DHCP server.

• No manual configuration required
• Works immediately on most networks
• The assigned IP may change if the DHCP lease expires (use static IP if stability is required)

Static IP

A DHCP reservation configured by IT provides a stable address without changing the gateway. Direct static-IP and hostname editing depend on the installed release; if the controls below are absent, contact support.

For enterprise environments, BACnet integrations, or anywhere a fixed address is required:

1. Go to Settings → Network
2. Select Static under IP Configuration
3. Enter the following:

1. Click Save — the device will apply the new settings (brief connectivity interruption expected)

When to use static IP:

• BACnet deployments (BMS needs a fixed address to communicate with C-Bridge)
• Enterprise environments with strict network policies
• Remote access configurations where port forwarding is in use
• Any installation where DHCP lease expiry would cause disruption

Hostname & Local Access

C-Bridge broadcasts its hostname via mDNS (Bonjour):

• Hostname: use the name printed on the device label, such as cbridge-XXXX.local
• Accessible from any browser on the same local network: http://cbridge-XXXX.local:3000

Changing the Hostname

If you're deploying multiple C-Bridge units on the same network, set unique hostnames to avoid conflicts:

1. Go to Settings → Network
2. Change the Hostname field (e.g., cbridge-floor2)
3. Save — the device is now accessible at http://cbridge-floor2.local:3000

Network Status

The Network page shows real-time connection information:

Enterprise Network Considerations

For commercial and enterprise deployments, coordinate with your IT team on the following:

VLAN Configuration

• C-Bridge can operate on a dedicated IoT VLAN for network segmentation

• Ensure the VLAN has:

• Internet access (for OTA updates and remote features)

• Access to the BMS network (for BACnet communication)

• mDNS/Bonjour forwarding (for cbridge.local hostname resolution across VLANs, if needed)

Firewall Rules

Coordinate these services with IT. Local ports should be reachable only by authorized clients on the LAN or VPN; the outbound cloud connection is separate:

DNS / mDNS

• mDNS (UDP 5353) must be allowed if using cbridge.local hostname resolution
• For cross-VLAN access, consider assigning a static IP and using that directly instead

Remote Access

C-Bridge supports remote access when the device has an active internet connection.

Cloud-Based Remote Access

• Accessible via the C-Bridge cloud portal (when available)
• Requires the device to have outbound HTTPS access (port 443)

VPN / IT-Managed Remote Access

• C-Bridge can be accessed over a corporate VPN if the device is reachable on the VPN network
• No additional configuration is required on C-Bridge — network routing is handled by IT

Remote Access Planning

Use the supported cloud access workflow or an IT-managed VPN. Do not expose the gateway's local HTTP, API, WebSocket, or BACnet ports directly to the public internet.

Troubleshooting Network Issues

Cannot Access C-Bridge Interface

• Confirm you are on the same local network
• Try accessing via IP address if cbridge.local doesn't resolve
• Check mDNS is enabled on your device (required for hostname resolution)
• Wait 2 minutes after a reboot before trying to access the interface

DHCP IP Keeps Changing

• Switch to a static IP (see above)
• Or configure a DHCP reservation in your router using the C-Bridge MAC address (found on the label under the device)

BACnet Client Can't Reach C-Bridge

• Confirm C-Bridge and the BMS are on the same subnet (or that routing between subnets is configured)
• Verify UDP port 47808 is not blocked by a firewall
• Use a static IP for C-Bridge in BACnet deployments

Related Articles

• C-Bridge Installation Guide — Physical network setup
• BACnet Integration — Port and network requirements for BACnet
• Firmware & Updates — Update process and connectivity requirements
• Troubleshooting Guide — Common network issues
• Static IP Configuration
• Firewall & IT Requirements
• Network Troubleshooting