Seriously, what's the deal with Traceroute?

submitted by empireOfLove2 to meshtastic 16 points | 11 comments 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?