Enable Private Network on Existing Vultr Server

SHARE:
Google+0
LinkedIn0
Pinterest0

Vultr offers private networking in all datacenter regions. All new servers deployed have the option of using private networking; it can be enabled by choosing the checkbox called “Enable Private Network” in the Optional Features section of the Deploy page. If you already have a server that does not have private networking enabled, you can follow below steps, which covers how to enable private networking on existing server.

1. Enable Private Network on Existing Vultr Server

– In your server management page, click IPv4 tab and then Enable Private Network button.

Vultr Enable Private Network

Your server will then incorporate the new private networking features.

2. Manually Configure Private Networking

You should now be logged into your server. The steps that follow will be dependent on which OS you are running. Follow the appropriate steps.

Note: replace ‘10.99.0.200’ in the examples with your IP

CentOS

Replace /etc/sysconfig/network-scripts/ifcfg-eth1 with the following:

DEVICE=eth1
 ONBOOT=yes
 NM_CONTROLLED=no
 BOOTPROTO=static
 IPADDR=10.99.0.200
 NETMASK=255.255.0.0
 IPV6INIT=no
 MTU=1450

Debian/Ubuntu:

In /etc/network/interfaces add the following lines:

auto eth1
iface eth1 inet static
 address 10.99.0.200
 netmask 255.255.0.0
 mtu 1450

FreeBSD:

In /etc/rc.conf add the following line:

ifconfig_vtnet1="inet 10.99.0.200 netmask 255.255.0.0"

Windows

Note: Windows may choose a different name for your private interface, make sure you check before trying with “Ethernet 2”

netsh interface ip set address name="Ethernet 2" static 10.99.0.200 255.255.0.0 0.0.0.0 1

3. Test the Configuration

Finally, restart your server and test the configuration by typing the following from another server in the same data center with private networking enabled:

ping private_ip

You should not receive any errors if you configured everything correctly.

Vultr Private Network:

  • Private network traffic is unmetered
  • Private networks are per-location (for example, a machine in New Jersey cannot communicate with a machine in Chicago)
  • Private networks only have your machines. You cannot communicate with other customer’s machines
  • You will need to manually configure your private network connection
  • You can use any IPs you like on the private network. Vultr assigns one IP by default, but you can ignore it and use other ones if you like.

See latest Vultr Coupon before creating account to get free credit!

Leave a Comment