-
Notifications
You must be signed in to change notification settings - Fork 8.3k
net: ipv6: Add support for stable IID addresses #80575
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
Merged
nashif
merged 4 commits into
zephyrproject-rtos:main
from
jukkar:devel/ipv6-stable-iid-with-slaac
Nov 16, 2024
Merged
net: ipv6: Add support for stable IID addresses #80575
nashif
merged 4 commits into
zephyrproject-rtos:main
from
jukkar:devel/ipv6-stable-iid-with-slaac
Nov 16, 2024
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
a33ea52 to
e0d73e7
Compare
Member
Author
|
pdgendt
reviewed
Oct 30, 2024
rlubos
reviewed
Oct 30, 2024
e0d73e7 to
7758804
Compare
Member
Author
|
7758804 to
1805f6a
Compare
pdgendt
previously approved these changes
Nov 1, 2024
This implements support for RFC 7217 which describes a method to have stable IPv6 Interface Identifiers to be used with IPv6 Stateless Address Autoconfiguration (SLAAC). The stable IIDs are used to provide enhanced privacy so that an IPv6 address configured using this method is stable within each subnet, but the corresponding Interface Identifier changes when the host moves from one network to another. This method is meant to be an alternative to generating Interface Identifiers based on hardware (MAC) addresses, such that the benefits of stable addresses can be achieved without sacrificing the security and privacy of users. Signed-off-by: Jukka Rissanen <[email protected]>
Add tests that verify that stable IIDs generate a proper IPv6 interface identifier described in RFC 7217. Signed-off-by: Jukka Rissanen <[email protected]>
Print information in "net ipv6" command how the SLAAC addresses are generated. There is the default legacy EUI-64 method (RFC 4862) or the stable method described in RFC 7217. Signed-off-by: Jukka Rissanen <[email protected]>
The short sleep (10ms) was not enough any more. Increase the sleep to 100ms so that system stabilizes between checks. Signed-off-by: Jukka Rissanen <[email protected]>
1805f6a to
d6d994e
Compare
pdgendt
approved these changes
Nov 2, 2024
rlubos
approved these changes
Nov 4, 2024
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 implements support for RFC 7217 which describes a method to have stable IPv6 Interface Identifiers to be used with IPv6 Stateless Address Autoconfiguration (SLAAC). The stable IIDs are used to provide enhanced privacy so that an IPv6 address configured using this method is stable within each subnet, but the corresponding Interface Identifier changes when the host moves from one network to another. This method is meant to be an alternative to generating Interface Identifiers based on hardware (MAC) addresses, such that the benefits of stable addresses can be achieved without sacrificing the security and privacy of users.
https://www.rfc-editor.org/rfc/rfc7217