From e5d9eb7c67dd459424d3ac3285b907dc0a826da8 Mon Sep 17 00:00:00 2001 From: Dale Ruane Date: Tue, 14 Apr 2026 16:37:40 +0100 Subject: [PATCH] docs: explain region home behaviour when unset Clarify that with no home region configured, auto-tagging is effectively disabled regardless of the region.autotag setting, and untagged floods fall back to the wildcard region's flood permission. --- docs/cli_commands.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/cli_commands.md b/docs/cli_commands.md index 1cbbc14e..116a4914 100644 --- a/docs/cli_commands.md +++ b/docs/cli_commands.md @@ -714,6 +714,8 @@ This document provides an overview of CLI commands that can be sent to MeshCore **Note:** The home region is used by the auto-tag feature (see `region.autotag` below) to stamp a transport code onto untagged flood packets this repeater receives, converting them from `ROUTE_TYPE_FLOOD` to `ROUTE_TYPE_TRANSPORT_FLOOD`. When selecting a home region, choose the **most specific region in the local region hierarchy that includes all nodes this repeater can possibly hear** (including via hops you intend to cover — see `region.autotag.max.hops`). Choosing a home region that is too narrow will cause unscoped packets originating from neighbouring regions to be tagged incorrectly; choosing one that is too broad defeats the purpose of scoping. +**When no home region is set:** the repeater has no scope to apply, so auto-tagging is effectively disabled regardless of the `region.autotag` setting — untagged flood packets are forwarded based on the wildcard (`*`) region's flood permission only. To participate in auto-tagging, both a home region must be configured here **and** `region.autotag` must be `on`. + --- #### View or change whether this repeater auto-tags untagged flood packets