networkd: avoid managing MAC addresses for veth devices#33
Merged
margamanterola merged 1 commit intoflatcar-masterfrom Jan 4, 2021
Merged
networkd: avoid managing MAC addresses for veth devices#33margamanterola merged 1 commit intoflatcar-masterfrom
margamanterola merged 1 commit intoflatcar-masterfrom
Conversation
When a veth device is created, the CNI in charge of bringing the device up will set a MAC address, if `MACAddressPolicy=permanent` is set, systemd will change it to a different one, causing dropped packets due to mismatches. With this change, the address set when the device is created will remain untouched by systemd. See flatcar/Flatcar#278 for more information.
pothos
approved these changes
Jan 4, 2021
jepio
pushed a commit
that referenced
this pull request
Feb 21, 2022
dracut/99emergency-timeout/timeout.sh: fix heredoc leak into arguments
zmrow
added a commit
to zmrow/bottlerocket
that referenced
this pull request
Mar 3, 2022
This change adds a default network configuration .link file that `systemd-udev` will use when configuring new interfaces. It contains the default list of policies that are used when naming interfaces, as well as the policy by which the MAC address should be set. Bottlerocket packages its own version of this file rather than the default from systemd for a few reasons. 1) Bottlerocket does not create/use a udev hwdb (we disable the option in systemd compile flags), so we remove this option from the NamePolicy list, 2) CNI plugins can be confused when MAC addresses change for virtual interfaces, so Bottlerocket sets the default MACAddress Policy to "none" which directs systemd not to attempt to manage the MAC. Hardware usually has a MAC, and veth devices used by CNI generally get a MAC generated by the plugin. Additional information about the MAC address issue: systemd/systemd#3374 (comment) flatcar/Flatcar#278 flatcar/init#33
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
2 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.
When a veth device is created, the CNI in charge of bringing the device up will set a MAC address. If
MACAddressPolicy=permanentis set, systemd will change it to a different one, causing dropped packets due to mismatches.With this change, the address set when the device is created will remain untouched by systemd.
See flatcar/Flatcar#278 for more information.
Testing done
I've tested this manually, by creating the equivalent /etc file. I haven't tested it using a generated image. We currently don't have any kola tests that catch this, because we aren't testing any CNIs that use this. We already have a rule in place for flannel, the only one that we do test.