Repository navigation
Conversation
puddly
force-pushed
the
puddly/fix-new-join-route-discovery
branch
from
November 9, 2026 16:51
0a1dd23 to
d398f6b
Compare
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
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.
This should fix #88.
We can temporarily try to directly contact a router that has joined via the coordinator. To keep this from affecting routing in general, we do so only for two link status periods, by which point normal routing logic should take effect.
I've also fixed the
route: Ignoring route reply from neighbor with zero outgoing costwarning by removing the check, it's unnecessary.