gnrc_ipv6_nc: adapt neighbor cache for different ND implementations#3744
gnrc_ipv6_nc: adapt neighbor cache for different ND implementations#3744OlegHahm merged 1 commit intoRIOT-OS:masterfrom
Conversation
a8eaf60 to
bfdcebe
Compare
|
Rebased to current #3628. |
bfdcebe to
a658040
Compare
|
Rebased to current master. Ready for review. |
There was a problem hiding this comment.
So, this module should not (never?) be defined if building for 6LoWPAN?
There was a problem hiding this comment.
If you only build for 6LoWPAN, yes. For border routers with ethernet support or similar, this might be included regardless and multi-NDP support kicks in.
There was a problem hiding this comment.
Maybe we can reflect this somehow in the Makefile.dep.
There was a problem hiding this comment.
It is already reflected (in #3748, that introduces 6LoWPAN-ND): https://github.com/RIOT-OS/RIOT/pull/3748/files#diff-cc423206e4b071a735d298217a657675R92
There was a problem hiding this comment.
I meant something that would explicitly remove this module from the used modules in a non-border router case.
There was a problem hiding this comment.
Not topic of this PR #3748 introduces this feature.
|
Travis seems to be happy, though no ACK was given... I'm confused |
|
I triggered Travis in advance in order to shorten things. |
|
However, ACK and go! |
gnrc_ipv6_nc: adapt neighbor cache for different ND implementations
Preparation PR for #3748 and follow-ups
Depends on #3628, since that one changes a lot in(merged)gnrc_ndp.c(including lines that the adaptations for this PR are touching) and I want to have as few as possible merge conflicts when rebasing #3134.gnrc_ipv6_nc_t::pktsis made option, 6LoWPAN-ND does not require queueing packetsgnrc_ipv6_nc_t::rtr_sol_timer: for unicast router solicitations to neighboring routers to re-acquire information that is about to be invalidated.gnrc_ipv6_nc_t::type_timeout: for the timed transition of NCE types (REGISTERED -> DELETE and TENTATIVE -> delete).gnrc_ipv6_nc_t::eui64: 6LoWPAN-ND uses the neighbor's EUI-64 to uniquely identify it, even if it uses the 16-bit short address for link-layer addressing.