Skip to main content

Using RegionMesh Geographic Scoping

Using RegionMesh Geographic Scoping

As your community grows within the larger RegionMesh national network, geographic scoping helps you manage channel capacity and create region-specific communications without polluting the national mesh.

The Problem Scoping Solves

On a nationwide mesh, every message without a scope floods all connected repeaters from Maine to California. This works fine for a small network, but as the network scales to thousands of repeaters, cross-country traffic consumes significant channel capacity. A neighborhood alert in Fargo, ND doesn't need to be relayed through repeaters in Miami.

How to Enable Regional Scoping

On each repeater in your regional network, configure the relevant region codes:

region put us
region put us-nd
region save
advert

This example configures a North Dakota repeater to serve both national US traffic and North Dakota-scoped messages.

Creating a Regional Channel

When your users send messages with the us-nd (or your region) scope set, those messages are only forwarded by repeaters that have that region configured. This creates an effective regional "channel" over the national infrastructure without requiring separate hardware or frequencies.

Registering a Metro Code

If your community covers a metro area not served by a state code alone (e.g., Dallas/Fort Worth spans multiple states), you can propose a community metro code. The process:

  1. Join the RegionMesh Discord at meshcore.gg
  2. Propose the code in the appropriate channel (format: lowercase, max 29 bytes, e.g., us-dfw)
  3. Achieve community consensus among local mesh operators
  4. The code is then registered and documented for others to use

Existing Metro Codes

See the RegionMesh Discord for the current complete list.

No comments to display

Back to top