Change AddrGenMode into enum #149
Open
+70
−9
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
Toorero
force-pushed
the
feature/addr_gen_mode_enum
branch
2 times, most recently
from
2eb3a71 to
a8f9849
Compare
cathay4t
requested changes
Mar 23, 2025
| match self { | ||
| Self::Eui64 => write!(f, "eui64"), | ||
| Self::None => write!(f, "none"), | ||
| Self::StablePrivacy => write!(f, "stable_secret"), |
There was a problem hiding this comment.
Even if "stable_secret" is used in iproute, I am more in favor of "stable_privacy". But if @cathay4t agrees on "stable_secret" that is 2 vs 1, so ignore the comment.
There was a problem hiding this comment.
Your call @cathay4t. I just outlined why I choose stable_secret. I'm fine either way.
Signed-off-by: Julius Rüberg <[email protected]>
Toorero
force-pushed
the
feature/addr_gen_mode_enum
branch
from
a8f9849 to
8d47556
Compare
|
Changes force-pushed. |
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.
This should fix #145