IPv6 privacy extension support #9905
Closed
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
jukkar
requested review from
pfalcon,
tarunkum and
tbursztyka
as code owners
Codecov Report
@@ Coverage Diff @@
## master #9905 +/- ##
==========================================
+ Coverage 52.41% 52.57% +0.16%
==========================================
Files 213 214 +1
Lines 26050 26281 +231
Branches 5621 5687 +66
==========================================
+ Hits 13654 13818 +164
- Misses 10138 10182 +44
- Partials 2258 2281 +23
Continue to review full report at Codecov.
|
|
status of this one? is it going to be updated and be ready for review? should it be closed? |
Looks like it could go to 1.15 as no one has had time to review it so far. |
|
This feature needs some pondering what to do when the IP address, that the application is using, changes. |
This creates support for IPv6 privacy extensions which is described in RFC 4941. This will also add API that can be used to add IPv6 prefixes to a white or black list privacy extension filter. Fixes zephyrproject-rtos#9349 Signed-off-by: Jukka Rissanen <[email protected]>
Have a timer which checks if there are any expired and temporary IPv6 addresses and removes them if any are found. Signed-off-by: Jukka Rissanen <[email protected]>
If IPv6 privacy extension is enabled, then we need to select proper public or temporary IPv6 source address when sending the packet. Signed-off-by: Jukka Rissanen <[email protected]>
Add tests that will make sure IPv6 privacy extension code works as expected. Signed-off-by: Jukka Rissanen <[email protected]>
When executing "net iface" command, print current status of IPv6 privacy extension if it is enabled in config file. The "net ipv6 ..." command prints IPv6 privacy extension information, and can add or delete IPv6 prefix filters. Signed-off-by: Jukka Rissanen <[email protected]>
jukkar
force-pushed
the
ipv6-privacy-ext-rfc-4941
branch
from
cb31b0c to
f25855b
Compare
|
Fixed merge conflicts. |
zephyrbot
added
area: API
|
Storing this to jukkar#20 as this is probably not going to be merged any time soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
This PR implements RFC 4941