> 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/deployment-resources/engineering-and-design-reference/network-ports-and-protocols.md). # Network ports and protocols Plan network access, validate controller connections, and diagnose communication issues on customer sites. Use this reference to plan, implement, and support Gallagher network communications. It helps Channel Partners and customers define firewall access, validate controller connectivity, and isolate site communication issues. ### Use these references * [Ports by component](/knowledge-hub/deployment-resources/engineering-and-design-reference/network-ports-and-protocols/ports-by-component.md) lists required ports, protocols, traffic directions, and version-specific firewall requirements. Use it during network design and when checking blocked communications. * [Controller link speeds](/knowledge-hub/deployment-resources/engineering-and-design-reference/network-ports-and-protocols/controller-link-speeds.md) lists supported Ethernet speeds and duplex modes. Use it to select compatible switch settings and diagnose controller network links. ### Apply the requirements at the customer site * **Design:** Share the required traffic flows with the customer network team before installation. * **Implement:** Configure firewall rules and switch ports for the installed controller and software versions. * **Troubleshoot:** Compare the configured network path with these requirements when a controller or client cannot communicate. --- # 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/deployment-resources/engineering-and-design-reference/network-ports-and-protocols.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.