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."
Verify that private networking is enabled for your cloud server. Your private network device is ens7. Your public network device is ens3.
Edit /etc/sysconfig/network-scripts/ifcfg-ens7
# nano /etc/sysconfig/network-scripts/ifcfg-ens7
Change 10.10.10.3 to the selected private IP address and replace the contents of ifcfg-ens7
with:
TYPE="Ethernet"
DEVICE="ens7"
ONBOOT="yes"
BOOTPROTO="none"
IPADDR=10.10.10.3
PREFIX=16
MTU=1450
Restart the connection, or reboot.
# nmcli con load /etc/sysconfig/network-scripts/ifcfg-ens7
# nmcli con up 'System ens7'
Verify that private networking is enabled for your cloud server. Your private network device is eth1. Your public network device is eth0.
Edit /etc/sysconfig/network-scripts/ifcfg-eth1
# nano /etc/sysconfig/network-scripts/ifcfg-eth1
Change 10.10.10.3 to the selected private IP address and replace the contents of ifcfg-eth1
with:
DEVICE=eth1
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=static
IPADDR=10.10.10.3
NETMASK=255.255.0.0
IPV6INIT=no
MTU=1450
Start the interface or reboot.
# ifup eth1
The Vultr API offers several endpoints to manage private networks.
You could earn up to $300 by adding new articles