You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, an entry in the fib (e.g., default route) is preferred over an entry in the prefix list.
This patch skips fib lookup if an entry in the prefix list exists.
(It is possible that the fib contains a matching entry with prefix length > 64. That would be skipped using this PR. But as that is a far more specific use case than a default route entry in the fib, I propose merging this and fixing lookup later.)
Doesn't the neighbor cache lookup trigger neighbor solicitations? If not, this patch just worked for me because the involved address were already in the cache...
If yes, the next hop is the target (as that prefix is configured to be reachable on that interface), and NDP will yield the next-hop l2.
Doesn't the neighbor cache lookup trigger neighbor solicitations? If not, this patch just worked for me because the involved address were already in the cache...
Technically wrong, but the result is the same: on 6LoWPAN there is no solicitation on address resolution; an address needs to be registered to the upstream router on addition to the interface. But, the WPAN is a mesh, so just because the prefix of the destination address is beyond one interface it does not need to be the next hop (so I guess the matching for prefixes >64 from the FIB is vital for the working of a 6LoWPAN).
But, the WPAN is a mesh, so just because the prefix of the destination address is beyond one interface it does not need to be the next hop (so I guess the matching for prefixes >64 from the FIB is vital for the working of a 6LoWPAN).
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
Area: networkArea: NetworkingType: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)
3 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.
kaspar030
added
Type: bug
Currently, an entry in the fib (e.g., default route) is preferred over an entry in the prefix list.
This patch skips fib lookup if an entry in the prefix list exists.
(It is possible that the fib contains a matching entry with prefix length > 64. That would be skipped using this PR. But as that is a far more specific use case than a default route entry in the fib, I propose merging this and fixing lookup later.)