Update next-hops based on traceroute result#8219
Merged
Merged
Conversation
thebentern
approved these changes
Oct 5, 2025
jeek
pushed a commit
to jeek/Meshtastic-Exploiteers-Hacker-Pager
that referenced
this pull request
Jun 30, 2026
Update next-hops based on traceroute result
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.
This updates next-hops for nodes in the original route towards a certain destination when the traceroute result came back. Brought up by @mihvoi (#7839 (comment)).
E.g., if the route is A->B->C->D and we are B, we can set C as next-hop for C and D. Similarly, if we are C, we can set D as next-hop for D. Lastly if we are A, we can set B as next-hop for B, C and D.
Tested with the interactive simulator, e.g. for the original sender:
And for the last node in the route: