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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable network on ipv6-only hosts #208
base: main
Are you sure you want to change the base?
enable network on ipv6-only hosts #208
Changes from 1 commit
cd2cf04
7e85fad
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this cause any slow-down as per the comment above ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It quite definitely causes a slow-down. Not sure how much. To me the question is more of whether it works at all. I cannot use
debos
at all as a result of this problem.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the late reply - I've been too busy to do any debos maintainance. Can you check if adding
MaxAttempts=10
(with the originalLinkLocalAddressing=no
) and possiblyIPv6AcceptRA=yes
works for ipv6-only host & for regular host ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LinkLocal=no with IPv6AcceptRA seems wrong; Just doing ipv6 link local addressing would make more sense;
Mind ofcourse this change was done in 2017 so things in systemd might have changed quite a bit. In particular the behaviour of networkd-wait-online could well have changed to not wait for all address families (which i think was the reason for the slowdown)
@helmutg when you say definitely a slowdown; Is that something that you actually noticed during usage or more an expectation :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay.
I cannot actually observe any delay with these settings, because
fakemachine
does not actually work in any way unless I change them. It is only that I expect a slowdown.So I did some more testing. With both
IPv6AcceptRA=yes
andLinkLocalAddressing=yes
, it works most of the time. I had at least one failure and suspect thatfakemachine.service
was being run before the network interface succeeded in configuring. Just settingMaxAttempts=10
does not improve the situation in any way.Adding
MaxAttempts=10
andIPv6AcceptRA=yes
also does not work. NeitherIPv6AccptRA=yes
norLinkLocalAddressing=yes
make it work in isolation. It is only when we combine them that it starts to work. Without the former, we don't get a default route and without the latter we don't get an IPv6 address assigned that could be routed.In all of this, when I say "does not work", what I mean is "Network is unreachable" being part of the error message.
Given further debugging, I think this is not the full solution. Network interfaces are not reliably configured when
systemd-networkd.service
is started. What is really needed here isnetwork-online.target
, but that's notWantedBy
orBefore
fakemachine.service
in any way. Of course addingnetwork-online.target
will make things even slower (again not measured in any way, just an expectation that adding more dependencies will take longer). But then in the context I am trying to use it, it currently does not work at all (due to not supplying any working IPv4 connectivity).