gnrc_ipv6_nib: queue packets that trigger probing on border router [backport 2021.10] #16949
Conversation
This file contains 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
(cherry picked from commit b869184)
miri64
requested review from
cgundogan,
jia200x and
leandrolanzieri
as code owners
miri64
added
Area: Kconfig
benpicco
approved these changes
Oct 5, 2021
miri64
deleted the
backport/2021.10/gnrc_ipv6_nib/fix/queue-pkts-on-6lbr
branch
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.
Backport of #16947
Contribution description
When probing for an unknown neighbor, the NIB on a 6LoWPAN border router currently drops the packet that triggered that probing in accordance with RFC 6775. However, it also does that on the upstream interface, as queuing support is removed at compile-time altogether. This adds an exception to the compile-time config
Testing procedure
Try to ping an Internet host via a border router from a 6LoWPAN host (see e.g. Task 8.5 of the release specs). The first message should go through with this PR, without it, the message will get lost.
Issues/PRs references
None, but the issue in #11988 might be related.