Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/guides/meshcore.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Meshcore Configuration

In addition to Meshtastic, there is now a growing cohort of Meshcore users in the Mountain Mesh community. While the two protocols cannot communicate with eachother, they both work on the same underlying principles. This page is dedicated to the findings and best practices for running Meshcore nodes from our community members.

## Network Congestion and Regions

Similar to Meshtastic, Meshcore can run into congestion issues. As more users join a network, it becomes more likely it is that message colissions will happen. And with nodes reaching from Atlanta up into West Virginia, we're experiencing more and more of these collisions.

This is where Regions come into play. Instead of Meshtastic's hop counts, Meshcore has the ability to limit messages within specific user-defined regions. This can be as large as an entire country or as small as a county. [Pinztrek on GitHub](https://github.com/pinztrek/mesher) is a Mountain Mesh community member and has documented their experiements with configuring regions for Meshcore repeaters.

Common regions within our community include:
```
- us-southeast
- us-ga
- us-ga-nw
- us-ga-ne
- us-ga-sw
- us-ga-se
- us-ga-atl
```

For more examples and configuration guides, see [piztrek's region congestion guide](https://github.com/pinztrek/mesher/blob/main/docs/regions.md).

## Software Recommendations and Quick Links

- [OpenHop Repeater](https://github.com/openhop-dev/openhop_repeater)

- [Mesh Stat](https://meshstat.com/#/home)
4 changes: 0 additions & 4 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,4 @@ There are two ways to check out our mesh in real time:
- [our MeshView instance](https://view.mtnme.sh/map)
- [our Malla instance](https://malla.mtnme.sh)

Here's what it looked like as of June 4th, 2025:

![MtnMe.sh MeshView Map](static/2025-06-04_mesh_map.png)

Both will let you get some information about what all those little dots represent, and will let you see new nodes that have come online since we last grabbed a screenshot.
Binary file removed docs/static/2025-06-04_mesh_map.png
Binary file not shown.
3 changes: 2 additions & 1 deletion mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,8 @@ nav:
- About: about.md
- Guides:
- MediumFast Migration: mediumfast.md
- Config: config.md
- Meshtastic Config: config.md
- Meshcore Config: guides/meshcore.md
- Filters: guides/filters.md
- 'Flashing the MeshToad or MeshTadpole': guides/flash-meshtoad-meshtadpole.md
- Ringtones: guides/ringtones.md
Expand Down