How to Configure a Private Network at Vultr

Introduction

When deploying a Vultr cloud server with a private network, you need to manually configure the private adapter. The examples shown in this guide are IPv4, but Vultr supports both IPv4 and IPv6. Vultr also supports multiple VLANs over a single private network interface with 802.1q tags. You'll find your server's information on the information page under Settings > IPv4. In the example below, the public network address is 192.0.2.123, and the private network address is 10.10.10.3. You'll find configuration samples for your server by clicking "View our networking configuration tips and examples."

---

Private Networking Notes

• When you enable private networking, you may use any RFC1918 private address as long as there are no conflicts with your other instances. Valid addresses include:
  • 10.0.0.0/8
  • 172.16.0.0/12
  • 192.168.0.0/16
• Private IP addresses in the customer portal are suggestions. You are not required to use the suggested private IP addresses.
• You can attach a maximum of 126 instances to a single private network. If you require more, please contact our engineering team.
• Private networks can not communicate between locations, regardless of IP addressing. For example, server instances in Miami can not see private networks in Dallas.
• Private networks do not have DHCP, and you must manually manage your IP address space or install a DHCP server on your private network.
• For optimal performance, set the private network adapter MTU to 1450 when configuring the NIC at the OS level.
• We also have guides to configure multiple private networks.

We have guides for popular operating systems. We also have guides to configure multiple private networks.

CentOS

For CentOS 6 through CentOS 8, please see the article How to Configure a Private Network on CentOS.

Debian

For Debian 7 through Debian 10, please see the article How to Configure a Private Network on Debian.

Fedora

For Fedora 24 through Fedora 31, please see the article How to Configure a Private Network on Fedora.

Fedora CoreOS

For Fedora CoreOS, please see the article How to Configure a Private Network on Fedora CoreOS.

FreeBSD

For FreeBSD 10 through FreeBSD 12, please see the article How to Configure a Private Network on FreeBSD.

OpenBSD

For OpenBSD, please see the article How to Configure a Private Network on OpenBSD.

Ubuntu

For Ubuntu 12.xx through Ubuntu 20.xx, please see the article How to Configure a Private Network on Ubuntu.

Windows Server

For Windows Server 2012 R2 through Windows Server 2019, please see the article How to Configure a Private Network on Windows Server.

Manage Private Networks via API

The Vultr API offers several endpoints to manage private networks.

Manage a network

• Create a new private network in a region.
• Get information about a private network.
• Update information for a private network.
• Delete a private network.

List all networks

• Get a list of all private networks in your account.

Manage private networks for an instance

• List the private networks for an Instance.
• Attach a private network to an instance.
• Detach a private network from an instance.