Add RPL relations table #790
Merged
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
thvdveld
force-pushed
the
rpl-relations-buffer
branch
from
c40401a
to
4b418a9
Compare
Codecov Report
@@ Coverage Diff @@
## master #790 +/- ##
==========================================
+ Coverage 80.09% 80.16% +0.06%
==========================================
Files 69 70 +1
Lines 28735 28841 +106
==========================================
+ Hits 23014 23119 +105
- Misses 5721 5722 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
The relation table will containt the next hop for each node in the RPL DODAG. For MOP1, this is the parent of each node. For MOP2, this is a neighbor of a sender. Signed-off-by: Thibaut Vandervelden <thvdveld@vub.be>
thvdveld
force-pushed
the
rpl-relations-buffer
branch
from
4b418a9
to
d02d002
Compare
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.
The relation table will contain the next hop for each node in the RPL DODAG. This is used in mode of operation 1, where the next hop is the parent of the node in the DODAG, and mode of operation 2, where the next hop is the neighbor of the sending node.