network: don't manage the loopback interface#24
Merged
pothos merged 1 commit intoflatcar-masterfrom May 17, 2021
Merged
Conversation
pothos
force-pushed
the
kai/networkd-unmanaged-lo
branch
from
5b31715 to
1d44d7f
Compare
The default network configuration is DHCP and was also applied to the loopback interface. This resulted in the loopback interface being in a "managed" state in networkd and sometimes caused the IP address to be deconfigured, resulting in errors when something tries to make use of the loopback interface, like resolved (see https://flaviutamas.com/2019/fixing-name-resolution-after-sleep). Exclude the loopback interface from the default configuration to make it "unmanaged".
pothos
force-pushed
the
kai/networkd-unmanaged-lo
branch
from
1d44d7f to
84af887
Compare
pothos
changed the title
pothos
added a commit
to flatcar-archive/coreos-overlay
that referenced
this pull request
May 14, 2021
This pulls in a change in the systemd network unit to ignore the loopback interface instead of managing its state which sometimes causes the address to be lost. flatcar/bootengine#24
Member
Author
|
I can still reproduce the |
dongsupark
approved these changes
May 17, 2021
pothos
added a commit
to flatcar-archive/coreos-overlay
that referenced
this pull request
May 17, 2021
This pulls in a change in the systemd network unit to ignore the loopback interface instead of managing its state which sometimes causes the address to be lost. flatcar/bootengine#24
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.
The default network configuration is DHCP and was also applied to the
loopback interface. This resulted in the loopback interface being in a
"managed" state in networkd and sometimes caused the IP address to be
deconfigured, resulting in errors when something tries to make use of
the loopback interface, like resolved
(see https://flaviutamas.com/2019/fixing-name-resolution-after-sleep).
Exclude the loopback interface from the default configuration to make
it "unmanaged".
Also see flatcar/init#40
How to use
See if
systemd-resolved[55175]: Failed to listen on UDP socket 127.0.0.53:53: Cannot assign requested addressmessages are gone in the case of endless loops in the initramfs (e.g., due to a non-reachable ignition URL), and if nothing else breaks because of the changeTesting done
for all platforms