Why: The mesh will become large enough that region scoping will need to be configured on every repeater. Region scopes need to be coordinated.
Inspiration comes from:
Proposal:
- Add a section in the nodes page, only for repeaters called "recommended settings" that includes a list of Meshcore CLI commands an admin can copy/paste to configure their repeater.
- Recommended settings will include region scope configuration, as well as arbitrary agreed upon settings for a region such as hash prefix mode, advert interval, agc reset interval, etc.
- There is a base layer for region scoping, similar to https://regions.meshcore.nz, of country code, state, county, and city/town.
- Additional regions and arbitrary settings would exist in a public GitHub repository. The format would be a set of JSON or YAML files that can be organized arbitrarily in directories. The files would include:
- A friendly name for the region
- Geo boundary, which would be a list of coordinates that enclose a region
- Regional representatives can submit PRs to manage their region's recommended settings
- Corescope would periodically read every file in the regional settings repository and use the data to populate the "recommended settings" section in the node page.
Future:
Connect to a client via USB/Bluetooth to be able to apply recommended settings to a repeater automatically. It would take the repeater's admin password, connect to the repeater, and apply the settings. There should be some retry mechanism per cli command sent to a repeater. And a mechanism to set and reset the path from the connected companion to the desired repeater.
Why: The mesh will become large enough that region scoping will need to be configured on every repeater. Region scopes need to be coordinated.
Inspiration comes from:
Proposal:
Future:
Connect to a client via USB/Bluetooth to be able to apply recommended settings to a repeater automatically. It would take the repeater's admin password, connect to the repeater, and apply the settings. There should be some retry mechanism per cli command sent to a repeater. And a mechanism to set and reset the path from the connected companion to the desired repeater.