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 or all that reliable, but messages still go through about 80-90% of the time, so why is the Traceroute module so bad? Is it just that much worse at handling packet failures compared to the message routine?
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.
Meshcore does now have client repeat mode which lets companions repeat like they do in meshtastic, but it does stick you on to a different frequency so that you don’t mess with the regular mesh.
Have a look at client repeat mode. May be worth a try. https://blog.meshcore.io/2026/02/13/off-grid-client-repeat-mode