> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-ethernet-bridge-mode.md). # Ethernet Bridge Mode Understand Ethernet Bridge Mode and its network behavior on a Controller 7000. Ethernet Bridge Mode, available from **Command Centre version 9.50 onwards**, allows the **Enhanced** and **High Sec** C7000 controllers to use their secondary Ethernet port as a **transparent bridge** to the primary port. This lets a second controller or an external device (for example a camera or laptop) connect through the bridging controller without needing a separate network switch at that location. *** #### What is Ethernet Bridge Mode and which controllers support it? * Requires **Command Centre version 9.50** and an Enhanced or High Sec 7000 Controller. * The controller operates as a **transparent Ethernet bridge**. All network traffic destined for the bridged network passes through without modification, regardless of traffic type or content. * The secondary Ethernet interface can connect a controller or an external device (for example a camera or laptop). * A **'Secondary Ethernet Link Failed' alarm** is raised when no active device is detected on the secondary port of a controller operating in Ethernet Bridge mode. *** #### What are the limitations of running a controller as a bridge? **No controller visibility to connected devices** * Devices connected through the secondary port cannot detect or retrieve any information about the bridging controller. **Downstream device offline impact** * Devices connected downstream of a bridging controller go **offline** if the bridging controller: * Restarts due to software upgrades * Restarts due to reset overrides or software faults * Loses power * Experiences upstream network connectivity issues **Not a redundancy mechanism** * Ethernet Bridge mode must **not** be used as a network redundancy or failover strategy. **Multiple downstream controllers, daisy-chain alarms** * When more than two controllers are connected in a daisy-chained bridge configuration, **multiple alarms may occur** during: * Simultaneous code downloads * Controller restarts *** #### What must I avoid when cabling a bridged network? 1. **Do not create a network loop.** When Ethernet Bridge mode is enabled, the secondary port forwards traffic to downstream devices. Ensure the secondary Ethernet port is **NOT** connected to the same network segment or switch as the primary Ethernet port. Incorrect cabling creates a network loop and may cause network disruption. 2. **Network setting changes cause drops.** In a daisy-chained Ethernet Bridge controller network, communication may drop or restart when network settings are changed, for example switching the controller network configuration from **Manual to Automatic** or vice versa. These changes generate a large number of events and alarms, which is expected behavior. 3. **Simultaneous code downloads in deep daisy chains.** Simultaneous code downloads across more than three daisy-chained Ethernet controllers can, in rare cases, cause a downstream controller to remain stuck in the download state if the upstream controller's network connection fails. **Recovery:** issue a **Push Config** override to the affected controller. *** 🔗 **Related** * [Limits](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-limits.md). Which C7000 variants support Ethernet bridging. * [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md). Bringing a downstream controller online through a bridge. * [Controller 7000](broken://pages/873trKCrdhjXzfqYdsdU). Variants, specifications, and accessories. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-ethernet-bridge-mode.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.