Network interface element not working
Ian Pilcher
arequipeno at gmail.com
Tue Apr 5 16:05:38 UTC 2022
On 4/5/22 10:12, Laine Stump wrote:
> Umm.... That's how it was intended to *not* work :-P. The whole point of
> the self-managed libvirt virtual networks is to setup a separate subnet
> that has all traffic routed via IP to the physical network. I'm
> impressed you've found a hack that works for you[*], but just be
> prepared to "pick up the pieces" if it breaks :-)
This is a lab setup. It only has to work for a few days.
> (I hope you've removed the DHCP service, DNS service, and for that
> matter even the IP address from the libvirt network definition. Also, is
> the host ethernet being used (i.e. does it have an IP address) prior to
> attaching it to the bridge? Normally when an ethernet is attached to a
> bridge, its IP configuration is moved to the bridge device, and the
> ethernet has no IP. I'm not sure what kind of connectivity oddities
> would show up if you left the IP address on the ethernet itself)
Actually, the physical interface is connected to a VLAN that I'm using
extend the existing virtual environment to some physical machines, so I
want to leave the virtual network otherwise unchanged, but have the
ability to add physical machines to the virtual network (if that makes
sense).
--
========================================================================
Google Where SkyNet meets Idiocracy
========================================================================
More information about the libvirt-users
mailing list