gnrc/ipv6/nib: automatically create 6ctx for downstream networks #21086
+45
−0
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.
Contribution description
When
gnrc_ipv6_auto_subnets
announces the creation of a downstream subnet to the upstream router, if that router is a 6lbr, it might as well create a compression context for that network.To also inform the downstream router about this compression context, send another RA to the downstream router, containing only the 6ctx information (to avoid creating a packet ping-pong loop if it also contained a prefix information option).
Testing procedure
An instance of
examples/gnrc_border_router
and one ofexamples/gnrc_networking
with both ZEP and TAP enabled (I used two instances of the border router with #21081 to only enable the ABR functionality of one at run-time).start 6LBR on-demand
Downstream node receives the
fd12::/16
prefix and creates afd12:1284:c87:1fb7::/64
prefix from it, sends this to the upstream router. Upstream router creates a compression context and response with yet another RA that contains the updated list of compression contexts.6ctx
on both nodes shows the same information:Issues/PRs references