> 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/configuration-client/site-installation/hardware/creating-controllers/configurable-ports-nat-solution/add-wan-configuration-to-the-controllers.md).

# Add WAN Configuration to the Controllers

Perform the following procedure to add WAN configuration to the Controller:

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Double-click on the appropriate Controller.

   The Controller Properties window displays to the **General** tab by default.
3. Select the **Network** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-00209b8884b9891ef587c1cfb724aedfb82dab0a%2Fnatsolutioncontroller_v890.png?alt=media)
4. If not already selected, click the **Enable NAT** checkbox.

   The **Enable NAT** section expands.
5. Enter the WAN Name/ID in the **Name/ID** field.

   The IP Address and the Port fields activate.

   **Note:** If the Controller is on the same network as the Command Centre server, this field should be the same as in the Server Properties.
6. Enter the WAN IP address in the **IP Address** field.
7. Enter the WAN port in the **Port** field.

   The valid range is 1024 - 65535.
8. Select **OK** to save your changes.


---

# 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/configuration-client/site-installation/hardware/creating-controllers/configurable-ports-nat-solution/add-wan-configuration-to-the-controllers.md?ask=<question>&goal=<user_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.
