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.
As per an idea of @mc-hamster, this adds a TraceRouteModule that traces the route a packet to a certain destination would follow. I will submit a PR to the CLI to add the necessary functionality. It works like this:
Only nodes that know the encryption key will be traced. Also note that a message may arrive via multiple routes due to duplication because of rebroadcasting. This will only show the route of the first packet containing the traceroute request that arrived at the destination.
I repurposed the existing RouteDiscovery message for it. It does not completely fit into the concept of a module though, because a device needs to alter the payload of a received packet even if it is not destined for you. Therefore I let the FloodingRouter call the module to update the route.
Here is a log of the destination node:
I also tested this up till 7 hops in the interactive simulator and that works fine.
Needs the TRACEROUTE_APP portnum to build successfully.