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:
- 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.
Verify that private networking is enabled for your cloud server. Your private network device is vio1. Your public network device is vio0.
Change 10.10.10.3 to the selected private IP address and replace the contents of
inet 10.10.10.3 255.255.240.0
!ifconfig vio1 mtu 1450
Restart the interface or reboot.
# sh /etc/netstart vio1
Manage Private Networks via API
The Vultr API offers several endpoints to manage private networks.
Want to contribute?
You could earn up to $300 by adding new articles