The problem
MeshCore delivers messages by flooding: every repeater relays every message once. In a small network that is perfect. In a large network, one message from Phuket would also be relayed by every repeater in Bangkok, Chiang Mai and beyond – using up airtime everywhere, although nobody there needs it. At some point the channel is simply full.
The solution: regions
A region (also called scope) is a label on a message. Each repeater keeps a list of regions it is willing to relay. A message scoped to th-phuket is only relayed by repeaters that know th-phuket – so it stays in Phuket.
Regions can be nested: th (Thailand) contains th-phuket, th-surat-thani, th-bangkok …
Rule of thumb: always use the smallest region that still reaches the people you want to talk to.
Names in Asia
Region names only work if everybody in an area uses exactly the same name. MeshCore Asia proposes this scheme:
- country: the two-letter country code, e.g.
th,vn - region: country code + region, e.g.
th-phuket,th-surat-thani,vn-hanoi
Names: lower-case letters, digits and - only, max 29 characters. You find the name for your area on each country and region page.
Setting it up
In the app: set the region scope of a channel (“Set Region Scope”). On app 1.43 or newer you can also set a default scope in the experimental settings – then everything you send is scoped.
On a repeater (CLI, e.g. for Phuket):
region put th *
region put th-phuket th
region save
On firmware older than 1.15, also run region allowf th and region allowf th-phuket. On 1.15 and newer, region default th-phuket scopes the repeater’s own adverts.
Messages without a region (older apps) are still relayed as before – regions can be introduced step by step.
More
- Region filtering and default scope – MeshCore blog
- Repeater CLI reference
- Why regions? – a good explanation with numbers