> 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/assign-external-ip.md).

# Assigning External IP Addresses to Internal Networks

Assign public external IP addresses to internal VergeOS networks with automatic routing rule creation for inbound connectivity.

External IP addresses can be assigned to internal networks. When an external IP is assigned, appropriate routing rules are created automatically.

## Assign an External IP to an Internal Network

1. From the **External Network Dashboard**, click **IP Addresses** on the left menu.
2. Click **New**.
3. In the ***Type*** field, select **Virtual IP**
4. In the ***IP Address*** field, enter the **public IP address**.
5. Enter the ***Hostname***.
6. Optionally, a ***Description*** can be entered to record additional administrative information.
7. In the ***Owner Type*** dropdown list, select **Network**.
8. In the ***Owner*** dropdown list, select the **name of the internal network**.
9. Click **Submit**.
10. While still on the **External Network Dashboard**, click **Apply Rules** on the left menu (to apply to the External Network).
11. Navigate to the **Internal Network Dashboard**
12. Click **Apply Rules** (to apply to the Internal Network).


---

# 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/assign-external-ip.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.