Fix random MAC address on reboot or when a VM/LXC is stopped or started. #96
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I noticed that the raspberry's MAC changed on every reboot or when a container/vm is started. Nothing too problematic, but this requires other devices to update their ARP table more often than needed.
This PR sets the MAC of vmbr0 to the one of eth0 in the network config. This should fix the issue for new users. Old users need to append their
/etc/network/interfaceswithFrom my knowledge, it is required to set the MAC of vmbr0 to one of the bridged ports (in this case eth0). Else it gets randomly generated, and the set address is ignored.