Get ready to learn more about Virtualizor KVM bridge. Our Virtualizor Support team is here to lend a hand with your queries and issues.

Virtualizor KVM bridge – An Introduction

Today we are going to take a look at managing the Network Bridge for KVM in Virtualizor. This involves creating a viifbr0 bridge, which in turn assumes eth0 as the Network Device and then detects the Netmask, IP,

and GATEWAY from

/etc/sysconfig/network-scripts/ifcfg-eth0 or /etc/network/interfaces

In case we have a different network device, we can configure the Virtualizor to use it as the Network interface to create the bridge.

Furthermore, we can change the settings via Virtualizor Admin Panel > Configuration > Slave Settings.

We can make the bridge permanent to ensure the bridge starts when the network is created. For instance:

First, we have to back up the ifcfg-eth0 with the following content. Here eth0 is the network interface and CentOS is the OS.

root# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
TYPE=Ethernet
HWADDR=00:25:90:98:35:90
IPADDR=10.0.0.93
NETMASK=255.255.255.0
GATEWAY=10.0.0.1
IPV6INIT=yes
IPV6ADDR=2607:f0d0:1002:0011:0000:0000:0000:0002
IPV6_DEFAULTGW=2607:f0d0:1002:0011:0000:0000:0000:0001
ONBOOT=yes

Next, we have to make a copy of it as seen below: root# cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0.bak

At this point, we have to create the bridge file with this:

root# vi /etc/sysconfig/network-scripts/ifcfg-viifbr0

Additionally, we have to copy the following part of ifcfg-eth0 file to ifcfg-viifbr0 file:

DEVICE=viifbr0
TYPE=Bridge
BOOTPROTO=static
IPADDR=10.0.0.93
NETMASK=255.255.255.0
GATEWAY=10.0.0.1
ONBOOT=yes
IPV6INIT=yes
IPV6ADDR=2607:f0d0:1002:0011:0000:0000:0000:0002
IPV6_DEFAULTGW=2607:f0d0:1002:0011:0000:0000:0000:0001

Next, edit the ifcfg-eth0 File to look like this:

DEVICE=eth0
HWADDR=00:25:90:98:35:90
IPV6INIT=yes
ONBOOT=yes
BRIDGE=viifbr0

Our experts would like to point out that we have to rename the interface route file to the ridge’s route file if our Server belongs to the Hetzner data center.

Now, it is time to restart the network.

Let us know in the comments if you need further help with the Virtualizor KVM bridge

Let us know in the comments if you need further help with installing OpenBSD on DigitalOcean.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

To sum up, our Support Engineers introduced us to the Virtualizor KVM bridge.