Get Involved

Join the MeshCore Network

Companion and/or Repeater

There are two ways to participate in the MeshCore network: as an active participant with a Companion, or by providing infrastructure with repeaters.

The choice is yours

Decide how you'd like to participate.


Settings

The 868 MHz frequency band is used.
It can be used without an amateur radio license under certain conditions.

Here in this region, the “EU/UK Narrow” preset is used. This corresponds to the following settings:

Frequency

869.618 MHz – This is the frequency used throughout most of Europe and the United Kingdom.

Bandwidth

62.5 kHz – This is the default setting used throughout almost all of Europe and the United Kingdom.

Spreading Factor

8 – This is the default setting used throughout most of Europe and the United Kingdom.

Coding rate

8 – This is the default setting for almost all of Europe and the United Kingdom.


Regions and Scopes

MeshCore introduces “region-based scoping” (available starting with version 1.10.0) to restrict packet distribution to specific geographic or logical areas, thereby reducing network congestion in large networks.

The Concept of Scopes and Regions

The concept of regions and scopes is very simple:

  • On repeaters, the regions for which they are responsible are defined
  • On Companions, regions are called scopes
  • Scopes can be retrieved from nearby repeaters via Companions or entered manually
  • In each channel, you can set
    a scope on the Companion to specify the region in which the message should be distributed
  • When a repeater receives a message, it checks the header for the scope to
    determine whether it should broadcast the message via the defined region
  • If it does not find the scope in its region list, the message is discarded

Regions are defined using Region CLI commands, which enable localized flooding and targeted message delivery. This is essential for scaling networks beyond the capabilities of peer-to-peer systems.

MeshCore Regions and Zones: Key Features

  • Region Definition: Users can define regions such as #MyRegion using the command region put {name} {parent} .
  • Scope Control: The flood scope feature restricts packet transmission to specific regions by %<scope> or % before the scope name (e.g., command%#Region).
  • Region Management: Commands such as region get search regions, region list displays configured regions and region save saves these settings.
  • Allowed Flooding: region allowf Enables the “Flood” (F) permission for specific regions, which is crucial for controlling message propagation, while region denyf removes this permission.
  • Global Scope: The icon * is used to represent the global or default range.

Regions can also be conveniently set using the management functions in the repeater’s admin section.

Regions and Areas

Various regions have been established to exchange messages within Europe.

For repeaters in Leipzig, for example, the following is recommended:

  • #de
  • #de-sn
  • #de-st (optional)
  • #de-th (optional)
  • #de-by (optional)
  • #de-central (optional)
  • #de-east (optional)
  • #de-sn-leipzig

You can find a comprehensive list of all common regions here: Overview of Regions

Further information:

If you use other regions or areas, please let us know by sending an email.


Naming Conventions

The following format is used for the names of devices such as repeaters and room servers:

<license plate>/<first byte of the admin ID>/<autonomous runtime (99 = solar, 24 = plugged-in)>/<free naming>

Of course, this convention is not mandatory.


Channels

In addition to the Public Channel, there are several other channels:

Public: 8b3387e9c5cdea6ac9e5edbaa115cd72

Countries:

  • #switzerland (Saxony, public)

Federal States:

  • #sn (Saxony, public)
  • #th (Thuringia, public)
  • #st (Saxony-Anhalt, public)

Cities/Regions:

  • #leipzig (Leipzig, public)
  • #zwickau (Zwickau, public)
  • #bsmesh (Braunschweig, public)
  • #hansemesh (Hamburg, public)
  • #berlin (Berlin, public)
  • #magdeburg (Magdeburg, public)
  • #dl-mitte (Central Germany/Harz Region, public)
  • #taunusmesh (Taunus Mesh, public)
  • #stuttgart (Stuttgart, public)
  • #hildesheim (Hildesheim, public)

National/International:

  • #meshcore
  • #bot (in some regions, there is a bot in this channel)
  • #ping (in some regions, there is a ping bot in this channel)
  • #announcements
  • #nerd-flea-market
  • #craft-corner
  • #test
  • #testing
  • #hamradio
  • #meshcorenetz (for fans of MeshCoreNetz.de)

Other channels/interest groups:

  • #nerd-flea-market
  • #jokes
  • #sports
  • #bees
     
  • #fire-department (interest group)
  • #THW (Interest Group)

Emergency Channels:

National/International:

  • #sos (recommended!)
  • #emergency

If you use any other channels, please let us know by sending an email.


Other Communities

MeshCore has a large community.
Many members coordinate through Telegram, WhatsApp, or the organization's website.

Social Media

Telegram:
@meshcorede

Discord:
meshcore.gg

Websites in Germany

meshcorenetz.de (MeshCore)

hansemesh.de (MeshCore)

loramesh-dresden.de (MeshCore)

taunus-mesh.de (MeshCore)

meshhessen.de (Meshtastic)

meshcore-de.fyi (Wiki)

mesh.dl5yda.de

Order without weighting

International Websites

meshcore.ch

meshcore.pt

Order without weighting