ifconfig: differentiate if to re-trigger dad on address updates (bsc#1177215) #857
Conversation
This file contains 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
mtomaschewski
added a commit
that referenced
this pull request
Feb 15, 2021
When we've just started or on each link-up (carrier detected) event, set all lease addresses tentative for the next commit to retrigger dad as we "may have moved to a new link".
mtomaschewski
force-pushed
the
retrigger-dad-or-not
branch
from
c884ca4
to
42b443f
Compare
|
Testsuite passes all tests. Manually tested the change on leap15.2, seems to work as expected. Thanks! |
rtorrero
approved these changes
Feb 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Re-trigger duplicate address detection when we may have moved to a new link, but skip it on
normal lifetime update / renew when it has been already performed (RFC8415, 18.2.10.1) to
not cause 1s packet loss during the detection.