Gnome Boxes Bridged Networking

[anvyko]

Hi!

So i need to use VMs for university and whatnot, and i decided to try Gnome Boxes. Unfortunately, i couldn’t ping between VMs and host, but i found a solution from Ivan Molodetskikh here: Support Bridged Networking to enable guests accessible from LAN (#546) · Issues · GNOME / GNOME Boxes · GitLab

On a fresh f36 install, libvirt-daemon-config-network was already installed, but i had to systemctl enable --now virtnetworkd-ro.socket in order to make bridged networking work in Boxes, which is great! But the maintainer of Boxes said in the above gitlab issue that it should work OOTB and was puzzled that it didn’t work in Fedora. So my question is, why isn’t it enabled by default?

[ilikelinux]

@anvyko

So my question is, why isn’t it enabled by default?

A lot of people use Virtualization to isolate an environment from their host and do not want to have access direct to the virtual env.

But I do agree, bridged network should be made easier for those who need it.

See if the following question I made helps you also with Boxes. I asked it for VMM.

Virtual Machine Manager | Bridged Network | Why so complicated to achiev?

If you want to bridge the physical network to the VM, you first have to create the bridge in NetworkManager and add the physical NIC as a port of the bridge. In this example, I’m bridging eth0 to a new bridge br0: # nmcli con add con-name br0 ifname br0 type bridge autoconnect yes ipv4.method auto ipv6.method auto # nmcli con add con-name br0-port ifname eth0 type ethernet slave-type bridge master br0 autoconnect yes Note that your existing connection for the ethernet interface will have to b…