If this is an Opinion please do not call the whole thing bridge.
Bridges are transparently connecting networks at layer 2. An non-
transparent bridge can't be called a bridge. Whatever it is. It's not a
bridge as bridge meant in networking terminology.
--
You received this bug notification
@Thomas,
can you try 'brctl stp br0 on' in the VM?
I reproduced your setup using an lxc container connected to a bridge,
and a separate network namespace inside the container. With stp off, I
could not ping the host or the outside world (without setting routes).
With stp on, I could ping the
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
** Changed in: libvirt (Ubuntu)
Status: New = Opinion
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/684424
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/684424
Title:
Bridges are not transparent for packets
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Setting promiscuous mode for all devices connected to the bridge does
not help. Trying to ping any system from the guest only shows the system
not reachable.
This error is, in my opinion, not only an annoying bug! It renders
kvm, qemu, xen, ... useless. It is something that has to be fixed!
The
