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?

  • tabarnaski@sh.itjust.works
    link
    fedilink
    arrow-up
    9
    arrow-down
    6
    ·
    10 days ago

    Traceroute uses ICMP echo requests (“pings”), and a lot of public routers have been blocking them since like 7-8 years.

    • HubertManne@piefed.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 days ago

      this was my though. people are talking about the quality of the networks and stuff and im thinking. I thought places blocked it so you generally would see you local stuff and then stars and once in awhile backbone things that sorta can’t block it because they are to important.