Resolving VirtualBox-based Vagrant boxes IP collisions

How to solve collisions of VirtualBox with virtual bridges on Fedora (e.g. when running Vagrant).

The problem occurs when trying to start VirtualBox-based Vagrant box due to IP collision with such a bridge. Vagrant would report something along the lines:

The specified host network collides with a non-hostonly network!
This will cause your specified IP to be inaccessible. Please change
the IP or name of your host only network so that it no longer matches
that of a bridged or non-hostonly network.

Vagrant actually runs /usr/bin/VBoxManage list bridgedifs command to determine the collision, but you will see it with ip addr show command as well.

$ /usr/bin/VBoxManage list bridgedifs | grep ""

One of the virtual bridges occupies address which is used by VirtualBox. In my case it’s virbr3.

To get rid of the interface you need to first bring it down and then remove:

$ sudo ip link set virbr3 down
$ sudo brctl delbr virbr3

Of course make sure you don’t need the interface anymore before doing that.


I wrote a complete guide on web application deployment. Ruby with Puma, Python with Gunicorn, NGINX, PostgreSQL, Redis, networking, processes, systemd, backups, and all your usual suspects.

More →