6lowpan: IPv6 next hop shouldn't supersede 6lo#3931
Merged
OlegHahm merged 1 commit intoRIOT-OS:masterfrom Sep 22, 2015
Merged
Conversation
If 6LoWPAN next hop determination and address resolution succeeds, it should not be superseded by IPv6 ND.
OlegHahm
added
Type: bug
Member
|
ACK and go if travis is happy. |
miri64
added
the
CI: ready for build
OlegHahm
added a commit
that referenced
this pull request
Sep 22, 2015
6lowpan: IPv6 next hop shouldn't supersede 6lo
Member
There was a problem hiding this comment.
Args… I only just now realized, that you also deactivate next hop determination for the case that the interface was given this way :/
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
If 6LoWPAN next hop determination and address resolution succeeds, it should not be superseded by IPv6 ND.