Virtual Private Cloud

Virtual Private Cloud (VPC)

A Virtual Private Cloud is private infrastructure you can build between your VPSes in our cloud. This is achieved by enabeling the creation of a Private VLAN you can assign Private IP address space to and thus enabling secure communication between the VPSes in the same VPC.

Steps to Enable a VPC between your VPSes

  1. In the VPS Interface create a VPC ID in the tab "Private Cloud"
  2. In the VPS Interface add VPS Members to the VPC
  3. !Reboot The VPSes!
  4. Manually add the ethx to the VPS's network-config (explained below)
  5. Assign your Private IP Address to the new network device (explained below)
  6. restart the network on the VPS (explained below)

If, for instance, you wish to create a VPC with the private IP range 10.10.10.x between a set of 4 VPS instances, then you assign each individual VPS to the VPC and reboot them all. After the restart the instances will have an extra network device available that can be configured for the VPC.

Make sure that all the VPSes in the same VPC share IP address in the same range, in our case:

VPS Private IP Address Netmask Network Broadcast Gateway
vps1 none
vps2 none
vps3 none
vps4 none

Network configuration For Linux:

The newly created interface is ethn, where n is the last numbered eth + 1, so if you have a basic VPS this could very well be (check with ifconfig on the prompt):


then create an entry for eth1.


for Debian/Ubuntu this is done by editing:


(if this file does not exists, please check the distro for the propper way to add an ethn)
adding an entry like:

auto eth1
iface eth1 inet static

!Caution: Don't provide a gateway in the standard VPC setup

after adding eth1, you could simply restart networking:

/etc/init.d/networking restart

For Centos create an ifcfg-etn entry in the /etc/sysconfig/network-scripts/ directory:

cd /etc/sysconfig/network-scripts/
vi ifcfg-eth1

with at minimum the following configuration:


after adding the ifcfg-eth1, you can simply restart the network by executing:

/etc/init.d/network restart
Windows Server 2003r2/2008/2008r2

For Windows is the setting of the new additional Network Adapter almost the same as above.

Only you can't get the new adapters with a reboot, you will have to ShutDown the server itself within de server.
"Start -> Shut Down computer". Our system detects the shutdown, add the new VPC adapter to it, and then starts up
the server with the additional adapter. After the server is auto-started, you can set the config of the new adapter;
Only fill in the following fields of the IPv4 properties in the new adapter:

Internet Protocol Version 4 (TCP/IPv4)
1) [x] Use the following IP address
2) Ip address: xx.xx.xx.xx
3) Subnet mask:
4) Default gateway: <Leave this setting empty!>
Other distros

if you have an other distro, please check the distro and version for the appropriate location and configuration for the new eth device.


General FAQ

Show all FAQs

OpenStack FAQ

Show all FAQs


Show all FAQs