> 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/zh/wang-luo/internal-layer3.md).

# 在 VergeOS 内部管理的内部网络（三层）

创建具有内置 DHCP、DNS、防火墙和路由功能、完全在 VergeOS 平台内管理的三层内部网络。

内部网络可以创建为 Layer2 或 Layer3。要创建一个 layer3 内部网络（其中可以在 VergeOS 中管理 DHCP、DNS、防火墙、路由和限速），请选择 ***静态*** 在 **IP 地址类型** 字段中。

![internallayer3.png](https://664309245-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpODKGSQETqL1gSqyxIq3%2Fuploads%2Fgit-blob-5d6e11b4ccea52cca1a1dd8828ab4d7169ff3145%2Finternallayer3.png?alt=media)

创建 layer3 内部网络的完整说明可参见： [**内部网络（一般说明）**](/run-the-platform/zh/wang-luo/internal-networks.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://docs.verge.io/run-the-platform/zh/wang-luo/internal-layer3.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.