> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/servers/details/networks.md).

# Networks

The specification matrix for the four network types, VPN protocols, firewall, VNF, and load balancer

Server network specifications. To understand each type of network and decide which one to use, go to Server networking in Concepts.

### Comparison of network types

| Characteristic         | Standard       | VPC                  | Layer 2  | Direct IP             |
| ---------------------- | -------------- | -------------------- | -------- | --------------------- |
| Type (CloudStack)      | Isolated       | VPC                  | Layer 2  | —                     |
| Virtual Router         | Yes            | Yes (shared)         | No       | No                    |
| DNS, DHCP, gateway     | Virtual Router | Virtual Router       | Your VNF | Your VNF              |
| NAT                    | Yes            | Yes                  | No       | No (direct public IP) |
| Firewall               | Virtual Router | Virtual Router       | Your VNF | Your VNF              |
| Multi-tier             | —              | Up to 3 (Super CIDR) | —        | —                     |
| Site-to-Site IPSec VPN | No             | Yes                  | No       | No                    |

### VPN

Available on networks **VPC**.

|                 |                                                                                                     |
| --------------- | --------------------------------------------------------------------------------------------------- |
| Types           | Site-to-Site IPSec · Remote access                                                                  |
| Negotiation     | IKEv1 · IKEv2 · Auto                                                                                |
| Auto behavior   | If we initiate the connection, it uses IKEv2; if it responds to it, it adapts to the other endpoint |
| Split tunneling | Requires IKEv2; creates a security association (SA) per remote network                              |

The limits (VPN per gateway, log retention) are in Limits and quotas.

### Firewall

Rules of **ingress**, **egress** and **Geo-IP** (allow or block by country). In Standard and VPC networks, the Virtual Router applies it; in Layer 2 and Direct IP, your VNF.

### Available VNFs

Network appliances that you deploy and operate yourself:

| VNF          | Provider   |
| ------------ | ---------- |
| FortiGate VM | Fortinet   |
| FireboxV     | WatchGuard |

They are deployed from the Marketplace (see Operating systems and applications).

### Load balancer

|                     |                                          |
| ------------------- | ---------------------------------------- |
| Algorithms          | Round-robin · Least-connections · Source |
| Persistent sessions | Yes (sticky sessions)                    |
| Supported network   | Standard                                 |


---

# 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.plenit.com/docs-en/productos/servers/details/networks.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.
