Regional Scoping with ISO Codes (MeshCore)
Regional Scoping with ISO Codes (MeshCore)
Regional scoping is part of the RegionMesh system for applying ISO 3166-2 geographic identifiers to MeshCore repeaters. It allows repeaters to filter message routing by region, reducing cross-country network congestion.
How It Works
- Messages without an explicit scope use a wildcard
*region and reach all repeaters regardless of region configuration. - When a message carries a scope: "Repeaters only forward messages when the scope precisely matches a configured region."
- This allows a regional community (e.g., Colorado) to create channels that stay within their region without polluting the national mesh.
Configuration Limits
- The number of regions configurable per repeater depends on firmware version. Refer to MeshCore release notes for current limits.
- Region identifiers: lowercase, maximum 29 bytes
- Minimum scope: country code (
us) plus state code (us-co)
CLI Configuration Example (Colorado)
region put us
region put us-co us
region saveThis configures the repeater to serve both the national US scope and the Colorado state scope.
Standard ISO 3166-2 Region Codes
| Code | Region |
|---|---|
us | United States (national) |
us-co | Colorado |
us-nd | North Dakota |
us-or | Oregon |
us-wa | Washington |
ca | Canada (national) |
Community-Defined Local Region Codes
Beyond ISO 3166-2 state/province codes, communities can define metro-area codes. These are registered by community consensus in the RegionMesh Discord:
| Code | Area |
|---|---|
us-dfw | Dallas/Fort Worth |
us-bay | San Francisco Bay Area |
us-atl | Greater Atlanta |
New local codes are established by community consensus and registered in the RegionMesh Discord at meshcore.gg.
After Changing Region Configuration
Always run advert after saving region changes to broadcast the updated configuration to the network immediately rather than waiting for the next scheduled advertisement.