From 8fcd7902c2ff8c822bfffbfa3e4e80af4145c49d Mon Sep 17 00:00:00 2001 From: agessaman Date: Sun, 19 Jul 2026 07:40:08 -0700 Subject: [PATCH] docs(cli): state the zero semantics of flood.max in the set help MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit OpenHop treats max_flood_hops 0 as unlimited while firmware's flood.max 0 forwards nothing — the inverse. Until that edge is decided alongside the policy-engine flood caps, say so in the help so a firmware-habituated admin does not set 0 expecting to disable forwarding (that is what 'set repeat off' is for) and silently get unlimited flooding instead. --- repeater/handler_helpers/mesh_cli.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/repeater/handler_helpers/mesh_cli.py b/repeater/handler_helpers/mesh_cli.py index de34220..40b7ee2 100644 --- a/repeater/handler_helpers/mesh_cli.py +++ b/repeater/handler_helpers/mesh_cli.py @@ -354,7 +354,7 @@ class MeshCLI: " set allow.read.only on|off Read-only access\n" " set advert.interval 60-240 minutes\n" " set flood.advert.interval
3-168 hours\n" - " set flood.max Max flood hops (max 64)\n" + " set flood.max Max flood hops (max 64; 0 = unlimited, unlike firmware)\n" " set path.hash.mode <0-2> Path hash mode (0=1B,1=2B,2=3B)\n" " set loop.detect Flood loop detection\n" " set rxdelay RX delay base (0-20)\n"