I’ve been trying to use it in my area to get a better idea of what path my packets are taking through the local mesh from different locations, seeing what links are weak and where another repeater might be useful.
But I swear it NEVER works. If there is more than a single hop in between me and my target node (whether it’s one I own or not), I never ever get a response. Nodes will be sending me power/environment information actively, and I get it A-OK, but when I try to traceroute-nada.
Once, i mean ONCE, I got a 2-hop response. And I run all my nodes at 7hop TTL since it’s very low traffic around here, so it’s not that.
My local mesh is not super dense, but messages still go through about 80-90% of the time, so why is the Traceroute module so bad?
I had similar issues with Meshtastic’s traceroute. Have you tried Meshcore? The design is a bit different in that it keeps the client nodes and repeaters separate, and repeaters are meant to be kept in more stable positions. I bring it up because in Meshcore you can manually select specific pathways to probe and analyze hops in greater detail. If there is an active Meshcore network in your area you might want to give it a try. It runs on the same hardware, so you can flip between systems, but the meshes cannot interact.
I’ve considered Meshcore. There is no Meshcore infrastructure in my area though, and Meshcore is also not ideal for my use case (which is going to involve a lot of mobile GPS tracker use in forest areas without infrastructure nodes, somewhere meshtastic shines a lot brighter).
I’m mostly just peeved that Meshtastic’s built in tools don’t work very well lol.