> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/networking/nat-1to1.md).

# Configuring NAT 1-to-1 Translation

Create a NAT 1-to-1 translate rule to map an external public IP address to an internal private IP address for full bidirectional traffic forwarding.

Before creating the translate rule to NAT an external IP to an internal IP:

* [**Define a static (private) IP for the destination VM**](/run-the-platform/networking/dhcp-static-lease.md)
* [**Assign an external IP to the internal network**](/run-the-platform/networking/assign-external-ip.md)

## Create a Translate Rule to NAT External IP to Internal IP

1. From the **Internal network Dashboard**, click **Rules** on the left menu.
2. Click **New**.
3. Enter a **Name** that will be helpful to future administration.
4. Optionally, a **Description** can be entered to record additional administration information.
5. In the **Action** dropdown, select ***Translate***.
6. In the **Protocol** dropdown, select ***ANY***.
7. In the **Direction** dropdown, select ***Incoming***.
8. **Define Source:** In the **Type** dropdown, select ***Any/None***.
9. **Define Destination:**
   * In the **Type** dropdown, select ***My IP Addresses***.
   * In the **IP Address** dropdown, select the external IP address.
10. **Define Target:**
    * In the **Type** dropdown, select ***My IP Addresses***.
    * In the **IP Address** dropdown, select the internal IP address (that was given a static IP address assignment).
11. Click **Submit** to save the rule.
12. Click **Apply Rules** on the left menu to put the new rule into effect.


---

# 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://docs.verge.io/run-the-platform/networking/nat-1to1.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.