[WIP] IPv6 privacy extension support #13
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
force-pushed
the
ipv6-privacy-ext-rfc-4941-wip
branch
6 times, most recently
from
14f88dd to
c1f29c7
Compare
jukkar
force-pushed
the
ipv6-privacy-ext-rfc-4941-wip
branch
2 times, most recently
from
3b90b42 to
80143e8
Compare
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. 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]>
The net_if_ipv6_prefix_get() function will return the proper prefix for a given IPv6 address and network interface. This is used when checking which source address should be returned to the caller. 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 new "net ipv6 ..." command can print general IPv6 information, and add or delete IPv6 prefix filters. Signed-off-by: Jukka Rissanen <[email protected]>
jukkar
force-pushed
the
ipv6-privacy-ext-rfc-4941-wip
branch
from
80143e8 to
b9439e1
Compare
jukkar
pushed a commit
that referenced
this pull request
Jan 15, 2020
- to get the update hal_nxp from PR #13 Signed-off-by: Ryan QIAN <[email protected]>
jukkar
pushed a commit
that referenced
this pull request
Jun 22, 2020
This makes the gatt metrics also available for gatt write-without-rsp-cb so it now prints the rate of each write: uart:~$ gatt write-without-response-cb 1e ff 10 10 Write #1: 16 bytes (0 bps) Write #2: 32 bytes (3445948416 bps) Write #3: 48 bytes (2596929536 bps) Write #4: 64 bytes (6400 bps) Write #5: 80 bytes (8533 bps) Write #6: 96 bytes (10666 bps) Write #7: 112 bytes (8533 bps) Write #8: 128 bytes (9955 bps) Write #9: 144 bytes (11377 bps) Write #10: 160 bytes (7680 bps) Write #11: 176 bytes (8533 bps) Write #12: 192 bytes (9386 bps) Write Complete (err 0) Write #13: 208 bytes (8533 bps) Write #14: 224 bytes (9244 bps) Write #15: 240 bytes (9955 bps) Write #16: 256 bytes (8000 bps) Signed-off-by: Luiz Augusto von Dentz <[email protected]>
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.
No description provided.