From b6ae8c94472678a8e95a44a9c29a3a3046c4aa09 Mon Sep 17 00:00:00 2001 From: Chris Barker Date: Mon, 1 Jun 2026 21:30:31 +0100 Subject: [PATCH] Updates Docs to reflect flood.max.unscoped behavior. --- docs/cli_commands.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/cli_commands.md b/docs/cli_commands.md index f63e6879..300a9ce0 100644 --- a/docs/cli_commands.md +++ b/docs/cli_commands.md @@ -617,6 +617,21 @@ This document provides an overview of CLI commands that can be sent to MeshCore **Default:** `64` +--- + +#### Limit the number of hops for an unscoped flood message +**Usage:** +- `get flood.max.unscoped` +- `set flood.max.unscoped ` + +**Parameters:** +- `value`: Maximum flood hop count (0-64) for a packet without a scope (no region set) + +**Default:** `0xFF` - indicates it hasn't been set, will track flood.max until it is. + +**Note:** An alternative to `region denyf *`, setting `flood.max.unscoped` to a lower value such as `3` would allow for local unscoped messages to propagate, while preventing noisy neighbors from flooding a local region. + + --- ### ACL