> 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.md).

# Configurable Ports - NAT Solution

### Introduction

The 'NAT Solution' allows Command Centre to communicate with multiple Controllers on different networks. This integration also enables Controllers on different networks to communicate with each other using the WAN IP address and the WAN port. Devices on the same network use the LAN IP address to communicate. If a device has a different WAN ID/Name, it will not be able to communicate with other devices configured with WAN on the same network.

### Deployment Architecture

**Note:** This diagram is a simplified example for a single remote site. Sites with more than one remote site will require additional routing configuration.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1b3d108a605a6f221809fbf17ddc106608863135%2Fnatsolution.png?alt=media)

<table><thead><tr><th width="193">WAN Properties</th><th>Function</th></tr></thead><tbody><tr><td>Name/ID</td><td>A label which determines the network the device is on. Any value for the Name/ID is acceptable. All devices on the same network must have the same WAN Name/ID. Two networks cannot have the same WAN Name/ID.</td></tr><tr><td>IP Address</td><td>The WAN IP Address is the NAT’s externally-addressable IP address. Also referred to as the public IP address.</td></tr><tr><td>Port</td><td>The WAN Port for a device must be unique within a network. The device’s WAN IP address the and WAN port are used by devices on different networks to establish connection.</td></tr></tbody></table>

### Prerequisites

Before you add the WAN configuration to the Command Centre server and the Controllers, it is recommended to set up port forwarding on your local and remote routers.

* Set up port forwarding on your local site router (Command Centre server site) to accept data on port 1072 from remote sites and forward it to Command Centre server. For each remote site, a separate rule is required.
* Set up port forwarding on your local site router (Command Centre server site) to accept data on the appropriate port and forward it to a local Controller.
* Set up similar port forwarding on your remote sites to allow Communication with the local and remote sites.

### Configuring remote site Controllers

To minimise configuration error, use one of the following methods to configure a new remote site Controller:

<table><thead><tr><th width="202">To...</th><th>then...</th></tr></thead><tbody><tr><td>configure remote site Controller using local subnet,</td><td><ol><li>Power on your Controller and bring it online (normally) using the same subnet configuration as the Command Centre server.</li><li><p>Once the Controller is online, configure the Controller (remote ones only) with the appropriate remote WAN and LAN IP addresses.<br><br><strong>Notes:</strong></p><ul><li>Only save your configuration once you have completed configuring both WAN and LAN IP addresses.</li><li>Once you have entered the remote IP addresses, the Controller will go offline as it can’t relate to those IP addresses.</li></ul></li><li>Ensure that DIP switch 6 is off to avoid loss of Configuration.</li><li>Disconnect the Controller from the Local network and connect it to the remote site network. The Controller will come online.</li></ol></td></tr><tr><td>access remote site Controller’s default IP interface using a browser,</td><td><ol><li>Turn the Controller DIP switches 2 and 3 on.<br><br><strong>Note:</strong> DIP switches 2 and 3 sets the Controller to the default settings.</li><li>Connect the Controller to a PC using an ethernet cable. Ensure that the PC is on the same subnet as the Controller.</li><li>Power on the Controller and use a browser to navigate to 192.168.1.199 (Controller’s default IP).<br><br><strong>Note:</strong> You will require a username and password, contact Gallagher tech support for these credentials.</li><li>Via this interface, configure the LAN IP address of the Controller.</li><li>Turn DIP switches 2 and 3 off.</li><li>On the Command Centre server, create a Controller, then add the WAN configuration.<br><br><strong>Note:</strong> Finish all Controller configuration, then save.</li></ol></td></tr></tbody></table>

### Configuration

To configure NAT Solution, perform the following procedures:

[Add WAN Configuration to the Command Centre Server](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configurable-ports-nat-solution/add-wan-configuration-to-the-command-centre-server.md)

[Add WAN Configuration to the Controllers](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)


---

# 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.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.
