Hello,
Just following up re: this bug. I think it's a pretty serious issue.
I am looking to work on this, but I am seeking some feedback and
direction from one of the core LXC devs.
- Do you agree with my analysis?
- Has anyone else worked on this already?
etc.
Thanks,
Derek
Hi,
Here we are using lxc intensively with bridges. Since we don't use STP, the
downtime for each a mac@ change is unnoticeable. In fact, we discovered it
when reading this mailinglist. After some test I can confirm that most of
the time we are spawning/destroying a container, the bridge's mac@
Francois-Xavier,
Thank you for your feedback.
I have seen the issue on two systems where STP is turned off. Here
is the /etc/network/interfaces entry for the particular bridge where
I've seen it the most; note the last line:
iface br0 inet dhcp
bridge_ports eth0
There is a behavior in the Linux kernel which can cause a bridge
device to change MAC address, thus causing a network blackout of several
seconds (while everybody ARPs the new MAC address flushes the old one).
This happens when bridging an enslaved interface, like we do with LXC.
