Following up on mesh communicating.
Sean Reifschneider
jafo00 at gmail.com
Sat Mar 21 22:15:02 UTC 2026
I've gone down that rabbit hole since my last post, and I've just upgraded
the Prospect and College repeater (moved up the tower ~12ft, upgraded to
RAK 1W), and my home (near Drake+Taft, increased elevation by around 5ft,
also upgraded to RAK 1W). Everything I'm doing these days is MeshCore
only, and the mesh definitely seems to be growing. A month to 6 weeks ago
I was getting no messages on the "Public" channel, now I'm getting 30-50 a
day from all up and down the Front Range.
Fort Collins is still pretty light on the number of repeaters, but it's
growing. I see a CreatorSpace repeater, it's not clear yet if the Prospect
and College repeater can reach it now that I've elevated it, I'll know more
in the next 24 hours as nodes send out advertisements and then I can pull a
neighbor list.
I set up a #linux hash tag channel. Those are public channels, so if
anyone is on MeshCore you can try hitting there. There's also #testing for
sending out test messages. Probably still a bit early to be expecting good
communications, but if you can put a repeater up somewhere high, like roof
top level, you probably have a good likelihood of being able to reach one
of the other repeaters and also fill in the mesh some.
If you've previously set up a meshcore node, you should consider upgrading
to 0.14.1, they are talking in the next month about making a fairly big
change to the mesh to go to 2 byte node prefixes because we have a lot of
collisions with 1-byte node prefixes right now. These are the primary way
that nodes in the mesh are identified, and I have 284 nodes in my contact
list, so 1 bytes is going to be sure to have collisions. Doesn't break
things, just means that when you view hop lists and set paths you run into
collisions.
I have a few extra repeaters if anyone has access to some particularly good
locations.
Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nclug.org/pipermail/nclug/attachments/20260321/c7fa9020/attachment.htm>
More information about the NCLUG
mailing list