> For the complete documentation index, see [llms.txt](https://docs.up-network.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.up-network.ch/documentation/guides/private-vxlan-virtual-extensible-lan-for-vps.md).

# Private VXLAN (Virtual Extensible LAN) for VPS

Private VXLAN (Virtual Extensible LAN)

#### Overview

**Private VXLAN** is a network virtualization option that allows multiple Virtual Private Servers (VPS) to communicate directly over a private Layer-2 overlay network, regardless of their underlying physical or IP infrastructure. It builds a *virtual LAN segment* on top of the service provider’s network using VXLAN technology. ([Wikipedia](https://en.wikipedia.org/wiki/Virtual_Extensible_LAN?utm_source=chatgpt.com))

This feature is provided **free of charge upon request** via a support ticket for customers with **2 or more VPS**.

The Private VXLAN lets you:

* Connect VPS instances in the same logical network (even across different hosts)
* Assign private IP addresses from one or more subnets that only exist within the VXLAN
* Communicate securely and privately between systems without exposing traffic to the wider internet

***

#### How It Works

**VXLAN (Virtual Extensible LAN)** is an overlay networking technology that encapsulates standard Layer-2 Ethernet traffic into Layer-3/UDP packets. This encapsulation enables systems on different physical or IP subnets to behave as if they are on the same *broadcast domain*. ([NetworkLessons.com](https://networklessons.com/vxlan/introduction-to-virtual-extensible-lan-vxlan?utm_source=chatgpt.com))

VXLAN uses a **VXLAN Network Identifier (VNI)** — a 24-bit identifier — to uniquely define each private network segment. Multiple VXLANs can coexist in the same physical infrastructure without interfering with each other. ([NetworkLessons.com](https://networklessons.com/vxlan/introduction-to-virtual-extensible-lan-vxlan?utm_source=chatgpt.com))

Within our platform:

* Your **Private VXLAN is isolated**, so traffic inside it is not visible outside of it.
* You can add **any number of VPS** to the same VXLAN.
* Each private subnet within a VXLAN behaves like a normal Layer-2 network: VPS can ping and route to each other just like they were connected to the same physical switch.

***

#### Default /24 and Custom Subnets

When a Private VXLAN is created for your account:

* We will automatically assign a **/24 network block by default** for private use.
* You may **change this default subnet** or create **additional subnets** (*also within the same VXLAN*) upon request.

For example:

| Feature            | Default                        |
| ------------------ | ------------------------------ |
| VXLAN created      | Yes, upon ticket request       |
| Default IP block   | /24 (e.g., 192.168.10.0/24)    |
| Additional subnets | Optional — client defined      |
| All subnets        | Part of the same VXLAN overlay |

This flexibility lets you manage multiple logical networks inside one VXLAN (for different environments, segmentation, services, etc.).

***

#### Use Cases

**Common uses** of Private VXLAN include:

1. **Flat network across multiple VPS** — Private Layer-2 connectivity without public exposure.
2. **Security-focused setups** — Back-end services communicate privately.
3. **Service clusters or micro-services** — Simplified networking for distributed systems.
4. **Custom IP addressing** — Use your own IP schema within the VXLAN.

***

#### Getting Started

1. Open a support ticket requesting **Private VXLAN**.
2. Provide:
   * Number of VPS you want in the VXLAN.
   * Desired subnet(s) (optional — we’ll assign a default /24 if not specified).
3. We’ll provision the VXLAN and assign a VNI and your subnet(s).
4. You can then configure IP addresses on your VPS and start using the private network.

***

### How to Configure Your Private VXLAN

#### Accessing the Private VXLAN

Once the **Private VXLAN option** has been activated on your account, you will see a **“Private VXLAN”** section appear in your VPS management panel:

👉 [**https://vps.upn.li**](https://vps.upn.li/)

<figure><img src="/files/BKD1SyKorE9wl3rhpOHO" alt=""><figcaption></figcaption></figure>

From this section, you can view and customize your VXLAN configuration, including the default subnet (/24) and any additional subnets you may have defined.

***

#### Assigning a VPS to the VXLAN

To attach a VPS to your Private VXLAN:

1. Go to the **VPS** you want to connect.
2. Open **Settings**.
3. Navigate to **IP Addresses** → **Virtual**.
4. Click **Add IP address**.
5. Select your **Private VXLAN** from the available options.

You can assign **up to 10 private IPv4 addresses from the VXLAN per VPS**.

Once at least one VXLAN IP is assigned, a **second network interface** will automatically appear inside your VPS, dedicated to the private network.

<figure><img src="/files/gj5HepC9DCl6SqAh0p7x" alt=""><figcaption></figcaption></figure>

***

#### Network Interface Configuration Inside the VPS

After assigning the VXLAN IP(s):

* The VPS will expose a **new network interface** (in addition to the public one).
* This interface is connected exclusively to the Private VXLAN.
* Traffic on this interface is fully isolated from the public network.

For users using **advanced networking setups**, we generally **recommend disabling automatic network configuration**inside the operating system.

This helps avoid conflicts or incorrect routing decisions made by the system, especially when working with:

* Multiple interfaces
* Custom routing
* Advanced firewall or service configurations

You can find the **exact IPv4 details** (address, subnet, gateway if applicable) directly in the VPS panel, and manually apply them to your OS network configuration.

***

#### Best Practices

* Use the VXLAN interface **only for private/internal traffic** between VPS.
* Keep public services bound to the main public interface.
* If you create multiple subnets, routing between them must be handled inside your VPS.
* A /24 subnet is recommended for flexibility and scalability, but can be adjusted if needed.

***

#### Notes & Limitations

* The VXLAN operates at **Layer-2 overlay** and does not replace public networking.
* VXLAN connectivity only exists between VPS added to the same network.
* Routing outside the VXLAN (internet/public networks) still requires normal network setup.
* Clients handle addressing and internal routing between subnets within the VXLAN themselves.\
  \
  \
  *Crédit: Image* [*https://www.ispsystem.com/docs/v6/virtual-networks*](https://www.ispsystem.com/docs/v6/virtual-networks)