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.

all 4 comments

sorted by: hot top controversial new old
[–] 3 points 1 year ago (3 children)

This may be a dumb question, but do you happen to know if you block a router on your client? Will you just not receive any packets that that router would otherwise send?

I tried it once and it still received packets from other nodes. So I'm not certain if that was intended behavior or not.

  • source
  • hideshow 3 child comments
  • [–] [S] 2 points 1 year ago (2 children)

    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. 🙂

  • source
  • parent
  • hideshow 2 child comments
  • 8 comments in c/selfhosted@lemmy.world view that post
    [–] 1 point 1 year ago
    [–] 5 points 1 year ago (6 children)

    Very cool.

    I wish I had a valid use case for my nodes, but they're basically just toys at the moment.

  • source
  • hideshow 6 child comments
  • [–] [S] 3 points 1 year ago (5 children)

    Yeah, so far the most prevalent thing around my area has been "it's a hobby for the sake of being a hobby." No one does anything terribly useful or important with it. I can tell you that I would certainly never rely on it as a form of emergency communication.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 1 year ago (4 children)

    Yeah its pretty spotty. A walky talkie would probably be better in an actual emergency. Im hoping meshcore or related projects will make it less spotty.

  • source
  • parent
  • hideshow 4 child comments
  • [–] [S] 2 points 1 year ago (3 children)

    Meshcore does address some of the biggest shortfalls of Meshtastic, but I absolutely HATE that they're positioned to either rugpull, or setup a perpetual "freemium" model. It's also not interoperable, so if Meshcore is to work, it needs the numbers like Meshtastic has.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 1 year ago (2 children)

    Agreed! I wish they could have worked with meshtastic instead of trying to get everyone off and using their project. Which is totally open source but not really.

    I think the next year or so will be interesting in the space. Im just sitting here with my little nodes making an impromtu weather station.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (1 child)

    What’s the difference between the two? Reading the GitHub for meshcore, it sounds exactly like meshtastic. What makes it better?

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 1 point 1 year ago

    The primary thing is rather than "dumb" flood routing, you can choose the path your message takes to its destination; as a repeater operator you can also choose the path it takes to repeat out. Its a slight compensation to people carelessly placing infrastructure nodes with poor configurations in poor places. Not perfect, but better. Adoption is much, much lower though, and the licensing is not copyleft.

  • source
  • parent