Răsfoiți Sursa

Updates Docs to reflect flood.max.unscoped behavior.

Chris Barker 2 luni în urmă
părinte
comite
b6ae8c9447
1 a modificat fișierele cu 15 adăugiri și 0 ștergeri
  1. 15 0
      docs/cli_commands.md

+ 15 - 0
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 <value>`
+
+**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