Fix #3200: Generate local mac address for the bridge #3414
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #3200. (require kernel v3.3 or later)
By default, the bridge attaches to the lowest mac address of the
interfaces it enslaves. However, the interfaces are added or deleted
as containers start or stop. So the bridge changes its mac address
from time to time, and causes the network disrupted temporarily.
Kernel 3.3+ and later allows the bridge to have its own mac address.
Once the bridge has its own mac address, it will stick with that one.
Signed-off-by: Tzu-Jung Lee roylee17@gmail.com