Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Advertise on LowEndTalk.com
How to create a SolusVM Private Internal Network
New on LowEndTalk? Please Register and read our Community Rules.

How to create a SolusVM Private Internal Network

XFS_BrianXFS_Brian Member
edited January 2013 in Tutorials

This guide shows you how to setup a Private Internal Network. This guide has been tested and works with KVM nodes. I have not tested this with XEN. This will not work on OpenVZ.

This guide presumes that you already have bridge-utils installed. To check, run the following:
rpm -q bridge-utils

You should get an output similar to the following:
bridge-utils-1.2-9.el6.x86_64

If you did not get any output like this, then it needs to be installed. Run the following:
yum install bridge-utils -y

Before setting up your Private Network, you will need to know the bridge name that you will use and the IP address range. In the guide, we will be using the bridge name of intbr0 and the IP range of 192.168.0.0/24

Create a new bridge file:
nano /etc/sysconfig/network-scripts/ifcfg-intbr0

Add the following to the file:
DEVICE=intbr0 ONBOOT=yes TYPE=bridge BOOTPROTO=static IPV4_FAILURE_FATAL=yes IPV6INIT=no IPADDR=192.168.0.1 NETMASK=255.255.255.0

Save and exit.

Restart the network service:
service network restart

Once the restart has completed, run the following to see the new bridge:
ifconfig

In SolusVM Master, goto Nodes > List Nodes. Click the name of the node that you setup the bridge for. Click on Internal IP Addresses. Fill the boxes using the information you used in your bridge.

Default Gateway = 192.168.0.1 (this is the IP address of the bridge)
Netmask = 255.255.255.0
Bridge = initbr0 (replace with the bridge name you used)

Click on Save.

Now you can add a single IP or a range of IP addresses. Do not add 192.168.0.1 as this is your default gateway.

To assign an IP to a virtual, this has to be done from the properties of that virtual. Once you are there, click on Internal IP. The new IP will not be assigned to the virtual until it has been rebooted. Once it is rebooted, the guest OS will not be able to use the new IP address. You, or the customer, will need to log in as root to add the IP. The steps to do this for CentOS are below.

Create a new device. Replace eth1 to match the device you are creating:
nano /etc/sysconfig/network-scripts/ifcfg-eth1

In this file, add the following:
DEVICE=eth1 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.0.10 GATEWAY=192.168.0.1 NETMASK=255.255.255.0

Save and exit.

Restart the network service:
service network restart

Check to see if the new device is listed by running the following. You should now see eth0, eth1, and lo:
ifconfig

Ping the default gateway:
ping 192.168.0.1

If the Internal IP is assigned to the virtual before you re-install the OS, there is no need to create the new device. SolusVM does this for you. It does not hurt to still log in and double check to make sure it was created correctly.

XFuse Solutions, LLC - Shared, OpenVZ & KVM VPS, & Dedicated Hosting - http://xfusesolutions.com

Comments

Sign In or Register to comment.