"Meshtrics:" A Nosy Neighbor's Guide to Meshtastic Airtime Metrics in Grafana
roguesecurity.dev
Start using Prometheus metrics from a PC-connected Meshtastic node to keep tabs on the local mesh in your area. Discover which nodes are misconfigured, hogging airtime, and see patterns in high-use times, as well as environmental changes!

This is a generic metrics post to leverage a spare ESP32 meshtastic node to ingest metrics into Grafana! We’ve had some congestion issues due to poor config in my area, and this has helped me pinpoint which nodes are causing the biggest problems, and block them at my repeater.

  • StarkZarnOPEnglish
    2·
    6 months ago

    That’s a great question!

    No, blocking a node – router or other – will only block packets originating from that node. All traffic that is forwarded by that node, but originating from others will still be received.

    Ultimately, the only place that blocking nodes strategically makes sense is on high utilization routers. If you’re just blocking nodes on a client, it’s not changing channel or airtime utilization for the rest of the mesh. That said though, if someone is harassing you then a block on a client is still fully worth it. 🙂

      • StarkZarnOPEnglish
        2·
        6 months ago

        My pleasure. It was a good question, I think I’ll even include a note on that in the post when I get home this evening and can edit.

        Cheers!