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[*
On 4/5/22 10:28 AM, Ian Pilcher wrote:
On 4/4/22 21:10, Laine Stump wrote:
That's not what the element in a is used for.
It's actual use is (in my opinion) not all that useful, which has led
to people assuming other functionality for it that doesn't exist.
Ah. Thanks for clarifying that.
On 4/4/22 21:10, Laine Stump wrote:
That's not what the element in a is used for. It's
actual use is (in my opinion) not all that useful, which has led to
people assuming other functionality for it that doesn't exist.
Ah. Thanks for clarifying that.
Anyway, if you want to have a bridge dev
On 4/4/22 2:08 PM, Ian Pilcher wrote:
I've added an interface element to a libvirt network, but it isn't
working. The interface is not being added to the bridge, even after the
system is rebooted.
That's not what the element in a is used for. It's
actual use is (in my opinion) not all that
I've added an interface element to a libvirt network, but it isn't
working. The interface is not being added to the bridge, even after the
system is rebooted.
# virsh net-dumpxml ocp4-net
ocp4-net
b5852945-9889-4d22-ba61-879125316cec
# brctl show
br
