Learn how to fix ”The viifbr0 is not started. Please run service via network start.” Our Virtualizor Support team is here to help you with your questions and concerns.

”The viifbr0 is not started Please run service virtnetwork start” | Solution

Have you run into the following message while working with a virtualized environment with Virtualizor?

The viifbr0 is not started. Please run service virtnetwork start.

Well, you are in luck! Today our Exerts are going to take us through the process of starting the “virtnetwork” service and troubleshooting common problems.

An Overview:

• How to Start the “virtnetwork” Service
• Adjusting the Network Interface Settings
• Verifying the Resolution
• Common Causes of viifbr0 Failure

How to Start the “virtnetwork” Service

To initiate the “viifbr0” network interface, we first need to start the “virtnetwork” service. We can do this by executing the following command:

service virtnetwork start

This command will start the “virtnetwork” service, which is essential for initializing the “viifbr0” interface.

Remember, we will need administrative privileges to run this command.

Recently one of our customers faced this error. Lets; take a look at how our Experts offred support.

Adjusting the Network Interface Settings

Initially, the network interface was set to `enp5s0f0` based on the configuration, but the issue persisted. Here’s what happened:

[root@bob123 ~]# service virtnetwork start
SIOCADDRT: Network is unreachable
Bringing up viifbr0 – OK
Waiting for 10 seconds…1…2…3…4…5…6…7…8…9…10
Checking network connectivity through ping to 4.2.2.1
connect: Network is unreachable
Internet connectivity check failed … Restarting normal network


Despite our Engineer restarting the network, connectivity remained unreachable. So, the next step was to inspect the configuration file:

vi /etc/sysconfig/network-scripts/ifcfg-enp5s0f0

The `netmask` was set to `/21`, which seemed incorrect.

Then, we changed the netmask value to ensure proper network connectivity.

We can modify the netmask with these steps:

1. First, locate the network configuration file. The configuration file for “viifbr0” is typically found in `/etc/network/interfaces` or `/etc/sysconfig/network-scripts/`.
2. Then, open the file using a text editor:

   vi /etc/sysconfig/network-scripts/ifcfg-viifbr0
3. Next, locate these lines:

   iface viifbr0 inet static
address
netmask
gateway

4. After that, change the netmask value to `255.255.248.0` (or the desired netmask):

   netmask 255.255.248.0
5. Then, save the changes and restart the networking service:

   service networking restart

Verifying the Resolution

After modifying the netmask and restarting the service, the issue was resolved:


[root@ bob123 ~]# service virtnetwork start
Bringing up viifbr0 – OK
Waiting for 10 seconds…1…2…3…4…5…6…7…8…9…10
Internet connectivity check successful viifbr0 – OK


Finally, by adjusting the netmask value to `255.255.248.0`, the network connectivity issue was successfully resolved, and Virtualizor’s “viifbr0” interface was brought up without further errors.


[root@ bob123 ~]# service virtnetwork start
Bringing up viifbr0 – OK
Waiting for 10 seconds…1…2…3…4…5…6…7…8…9…10
Internet connectivity check successful viifbr0 – OK


If we encounter similar issues, always ensure that network settings align with your infrastructure requirements and consult documentation or system administrators when necessary.

Common Causes of viifbr0 Failure

The viifbr0 network interface is crucial for Virtualizor’s networking functionality. If it fails to start, it can disrupt virtual machine connectivity, making troubleshooting essential. Here are some key reasons why viifbr0 might not start:

• Misconfigurations in the network settings are one of the most common causes of **viifbr0** failures.
• Conflicts between viifbr0 and other network interfaces can prevent it from starting.
• Furthermore, certain packages and kernel modules are required for viifbr0 to function correctly. Missing or improperly loaded dependencies can result in failures.
• Firewalls or security rules may block viifbr0 from establishing connections, causing network failure.
• If SELinux is enabled, it may prevent viifbr0 from starting, depending on the security policy.
• Also, routing problems can prevent viifbr0 from communicating with other networks, resulting in startup failure.
• The routing table may contain incorrect or missing routes, causing **viifbr0** to be unable to find the correct gateway.
• System resource exhaustion can also prevent viifbr0 from starting, especially if there is insufficient memory or CPU resources.
• Additionally, if the host system is low on memory or processing power, the viifbr0 interface may not start.

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

Conclusion

By adjusting the netmask value to 255.255.248.0, we can easily fix the network connectivity issue.

In brief, our Support Experts demonstrated how to fix ”The viifbr0 is not started. Please run service via network start.”