Skip to content

KVM Private Internal Network Setup

User Contributed Documentation
Credit: Brian Oliver, XFuse Solutions LLC

Note: Private Internal network can be configured only for KVM virtualization.

Note: If VPS with internal network is migrated to other KVM node (with or without private internal network) - internal network configuration of VPS will break. It will be required to reconfigure internal network of VPS according to available internal IP range of the new KVM node.

Before setting up your Private Network, you will need to decide on the bridge name that you will use and the IP address range. IP range can be anything from private IP ranges. In the guide, we will be using the bridge name of intbr0 and the IP range of 192.168.0.0/24.

1. Access the KVM node where it is required to setup private network for VPS over SSH.

2. Make sure bridge-utils package is installed:

yum install bridge-utils -y

3. Create a new bridge file:

nano /etc/sysconfig/network-scripts/ifcfg-intbr0

4. 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

Note: replace intbr0, 192.168.0.1 and 255.255.255.0 with the required configuration.

5. Save and exit.

6. Restart the network service:

service network restart

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

ifconfig

8. Rename /usr/local/solusvm/data/config.ini.example to /usr/local/solusvm/data/config.ini:

mv /usr/local/solusvm/data/config.ini.example /usr/local/solusvm/data/config.ini

9. Open config.ini:

nano /usr/local/solusvm/data/config.ini

10. Change text in the next section with following one:

;; When writing the internal network configuration within the virtual
server
;; don't add the gateway variable
;domain_simple_internal_network = false

;; When writing the internal network configuration within the virtual
server
;; don't add the gateway variable
domain_simple_internal_network = true

11. Save and Exit.

12. Open SolusVM Administrator interface.

13. Open SolusVM > Nodes > node for which private network is required > Internal IP Addresses:

InternalIPAddresses

14. 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)

InternalIPsettings

15. Click Save.

16. Add a single IP or a range of IP addresses:

Note: Do not add 192.168.0.1 as this is your default gateway.

InternalIPAdded

After this step you can assign internal IP addresses.

Important notes:

  • Internal IP address can be assigned only on existing VPS.

  • Only one internal IP address can be assigned to a VPS.

17. Open SolusVM > Virtual Servers > the required VPS > Internal IP:

InternalIPVPS

18. Select the required internal IP address in IP Address field and click Add.

Note: MAC address is generated automatically.

InternalIPVPS

19. Reboot VPS via SolusVM > Virtual Servers > VPS > Reboot.

After assigning internal IP address to VPS and rebooting it - it is required to manually add network interface for internal IP address inside VPS.

Note: these steps are not required if you reinstall VPS after assigning internal IP to it.

1. Access VPS with the assigned internal IP via SSH.

2. Create a new device. Replace eth1 to match the device you want to create:

nano /etc/sysconfig/network-scripts/ifcfg-eth1

2. Add the following:

DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.0.3 
NETMASK=255.255.255.0

Note: replace 192.168.0.3 with the correct assigned internal IP.

3. Save and exit.

4. Restart the network service:

service network restart

6. Ping the default gateway:

ping 192.168.0.1
Back to top