Dear Peter, Hi Fajar,
* Is even LXC not needed to reproduce the issue but just a bridge on a bound
and some other devices?
* Did this issue appear if you use a higher MAC prefix than 64:... for the
veths?
May you dump the arp traffic (maybe together with icmp) on the host? I'm
interested in
On 09/10/2015 11:14 PM, Guido Jäkel wrote:
* Is even LXC not needed to reproduce the issue but just a bridge on a bound
and some other devices?
I have not been able to reproduce the problem except between containers
running on different hosts. Behavior is the same for lxc and libvirt-lxc.
*
On 09/11/2015 12:08 PM, Andrey Repin wrote:
So, have you tried getting rid of the bridge in first place?
The problem isn't the bridge per se, it's the bond mode. If I use
active-backup the veth->bridge->bond path from container to container
works as expected. Bond modes using load balancing
Greetings, Peter Steele!
>> * Is even LXC not needed to reproduce the issue but just a bridge on a bound
>> and some other devices?
> I have not been able to reproduce the problem except between containers
> running on different hosts. Behavior is the same for lxc and libvirt-lxc.
>> * Did this
On 09/10/2015 07:57 PM, Fajar A. Nugraha wrote:
If I read the bug report correctly, it's not moved to lxc. Rather, KVM
is not required to reproduce it, using lxc is enough to trigger the
bug. Using KVM will of course still trigger the bug as well.
Sorry, I didn't mean the bug was moved to lxc,
