Virtual Private Cloud

From XLS Hosting Wiki

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

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

Configuration

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
vps 1	10.10.0.10	255.255.255.0	10.10.0.0	10.10.0.255	none
vps 2	10.10.0.11	255.255.255.0	10.10.0.0	10.10.0.255	none
vps 3	10.10.0.12	255.255.255.0	10.10.0.0	10.10.0.255	none
vps 4	10.10.0.13	255.255.255.0	10.10.0.0	10.10.0.255	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):

eth0
lo

then create an entry for eth1.

Debian/Ubuntu

for Debian/Ubuntu this is done by editing:

/etc/network/interfaces (chattr -i /etc/network/interfaces first. chattr +i /etc/network/interfaces after the edit)

(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
 address 10.10.0.10
 netmask 255.255.255.0
 broadcast 10.10.0.255
 network 10.10.0.0

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

after adding eth1, you could simply restart networking:

/etc/init.d/networking restart

CentOS

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:

TYPE=Ethernet
DEVICE=eth1
IPADDR=10.10.0.1
NETMASK=255.255.255.0
BROADCAST=10.10.0.255
NETWORK=10.10.0.0
ONBOOT=yes

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: 255.255.255.0
4) Default gateway: <Leave this setting empty!>

=LET OP!= Er is bij ons een bug bekend. Als u geen connectiviteit heeft tussen uw Windows VPS'en via de VPC moet u bellen
of emailen met de supportdesk met vermelding van uw VPS nummers. Iemand van support kan dan uw VPC connectiviteit activeren.

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.

Virtual Private Cloud

From XLS Hosting Wiki

Contents