Internal Network

From Virtualizor Wiki
Jump to: navigation, search

Overview

This guide shows you how to create an additional network which can be used to give a VM additional Internal IP Addresses.
Virtualizor's IP Pool system supports this on all Virtualization.


Creating the Bridge

Although Virtualizor creates its own Network Bridge, you will need to create the additional Bridge to use it.
Create the bridge with whatever name you want. The following is a bridge created for internal networks with the name intbr0.
File : /etc/sysconfig/network-scripts/ifcfg-intbr0

DEVICE=intbr0
ONBOOT=yes
TYPE=Bridge
BOOTPROTO=static
IPADDR=192.168.1.1
NETMASK=255.255.255.0


IF you have a secondary NIC for interserver internal network, you can set the following :
Assuming you have eth1 as the secondary NIC :
File : /etc/sysconfig/network-scripts/ifcfg-eth1

DEVICE=eth1
ONBOOT=yes
TYPE=Ethernet
IPV6INIT=no
USERCTL=no
BRIDGE=intbr0

Restart the network service:

root> service virtnetwork restart

Please check if the new intbr0 is now up and running with the following command.

ifconfig

Creating IP Pool

Now you simply need to create an IP Pool in Virtualizor.
The following is a screenshot of a sample IP Pool :

Internal IP Pool.png

That is it. You are now set to assign IPs.

Assigning Internal IPs

After your IP Pool is created, you can now assign the Internal IP Addresses.
You can specify the same in your WHMCS billing module or while creating / editing a VM in Virtualizor.
The following is a screenshot of the Virtualizor VPS Creation wizard :

Internal IP Address Assign.png

Virtualizor will assign the network IPs to the VM when the VPS is started.
The VM will have two network interfaces i.e. one for the public IP addresses and the other for the internal IP network.

Multiple Nodes Range

If your network setup is correct you can also use the IP Pool across multiple nodes.
While creating the IP Pool, just choose "All Servers" or the "Node Group" accordingly.