Add altpath replies and flood channel hop gates
This commit is contained in:
1 parent
f747f96739
commit
9908d2b73e
6 files changed
+349
-66
No files matched your search
+39
-9
@@ -781,9 +781,11 @@ send text.flood checking ridge link
|
||||
|
||||
**Forwarding behavior:** Repeater firmware only. The repeater still receives and
|
||||
logs the packet when logging is enabled; this only blocks retransmission.
|
||||
This is checked before `flood.channel.block` and applies to every flood
|
||||
`GRP_DATA` packet regardless of channel key. Flood group text (`GRP_TXT`) is
|
||||
unaffected.
|
||||
This is checked before `flood.channel.block` and applies to flood `GRP_DATA`
|
||||
packets regardless of channel key, subject to `flood.channel.block.hops`.
|
||||
Flood group text (`GRP_TXT`) is unaffected by this setting.
|
||||
|
||||
`get flood.channel.data` includes the active hop gate as `h=all` or `h>N`.
|
||||
|
||||
---
|
||||
|
||||
@@ -792,10 +794,12 @@ unaffected.
|
||||
- `get flood.channel.block`
|
||||
- `get flood.channel.block.<n>`
|
||||
- `get flood.channel.block <name|8_hex_prefix>`
|
||||
- `set flood.channel.block <key> <name>`
|
||||
- `set flood.channel.block.<n> <key> <name>`
|
||||
- `set flood.channel.block #channel`
|
||||
- `set flood.channel.block.<n> #channel`
|
||||
- `get flood.channel.block.hops`
|
||||
- `set flood.channel.block <key> <name> [h=<all|1-7|default>]`
|
||||
- `set flood.channel.block.<n> <key> <name> [h=<all|1-7|default>]`
|
||||
- `set flood.channel.block #channel [h=<all|1-7|default>]`
|
||||
- `set flood.channel.block.<n> #channel [h=<all|1-7|default>]`
|
||||
- `set flood.channel.block.hops <all|1-7>`
|
||||
- `del flood.channel.block.<n>`
|
||||
- `del flood.channel.block <name|8_hex_prefix>`
|
||||
|
||||
@@ -803,8 +807,11 @@ unaffected.
|
||||
- `n`: Slot number from `1` to `15`.
|
||||
- `key`: 128-bit or 256-bit channel key as hex.
|
||||
- `#channel`: Public hashtag channel name; derives the 128-bit channel key from the hashtag and is stored as the row name.
|
||||
- `name`: Local label for hex-key rows. Not needed for `#channel`; any extra text after `#channel` is ignored.
|
||||
- `name`: Local label for hex-key rows. Not needed for `#channel`; extra text after `#channel` is ignored unless it is a hop setting.
|
||||
- `8_hex_prefix`: First 4 bytes of the derived channel hash, shown by single-entry `get`.
|
||||
- `all`: Block matching flood channel packets at any received flood hop count.
|
||||
- `1-7`: Maximum received flood path hash count to repeat. Matching packets over this hop count are blocked.
|
||||
- `default`: Row inherits the global `flood.channel.block.hops` setting.
|
||||
|
||||
**Slot behavior:** Without `.n`, `set flood.channel.block` updates an existing
|
||||
row with the same derived channel prefix or name, otherwise it uses the next
|
||||
@@ -815,7 +822,26 @@ writes that slot.
|
||||
flood `GRP_TXT` and `GRP_DATA` channel packets. The repeater still receives and
|
||||
logs the packet, but it does not retransmit it when a configured block entry can
|
||||
validate/decode it. If `flood.channel.data` is `off`, all flood `GRP_DATA`
|
||||
packets are blocked before this per-channel check runs.
|
||||
packets over the hop gate are blocked before this per-channel check runs.
|
||||
|
||||
**Hop gate:** `flood.channel.block.hops` defaults to `all`, which preserves the
|
||||
original behavior. When set to `N` from `1` to `7`, both `flood.channel.data off`
|
||||
and block rows that inherit the global setting only block packets whose received
|
||||
flood path hash count is greater than `N`; packets at `N` hops or lower can
|
||||
still repeat. For example, `set flood.channel.block.hops 1` repeats zero-hop and
|
||||
one-hop matches but blocks two-hop and longer matches.
|
||||
|
||||
Each block row can override the global hop gate with `h=<all|1-7|default>`.
|
||||
For example, `set flood.channel.block #wardriving h=3` blocks `#wardriving`
|
||||
matches above three hops, while `set flood.channel.block #bot h=7` blocks
|
||||
`#bot` matches above seven hops. Use `h=default` to make the row inherit the
|
||||
global setting again.
|
||||
|
||||
`get flood.channel.block` includes the global default first, then adds per-row
|
||||
overrides as `/h>N` or `/h=all`; inherited rows do not show a suffix. Single-row
|
||||
`get` replies include that row's stored hop mode as `h=def`, `h=all`, or `h>N`.
|
||||
List replies truncate displayed row names only when the full list would exceed
|
||||
the remote-management response limit.
|
||||
|
||||
**Matching behavior:** Each block entry stores the first 4 bytes of the derived
|
||||
channel hash for display and lookup. Current group packets carry only the first
|
||||
@@ -829,7 +855,11 @@ MAC/decrypt.
|
||||
```
|
||||
set flood.channel.block #test
|
||||
set flood.channel.block.2 9cd8fcf22a47333b591d96a2b848b73f #test
|
||||
set flood.channel.block.hops 3
|
||||
set flood.channel.block #wardriving h=3
|
||||
set flood.channel.block #bot h=7
|
||||
get flood.channel.block
|
||||
get flood.channel.block.hops
|
||||
get flood.channel.block #test
|
||||
del flood.channel.block.2
|
||||
```
|
||||
|
||||
@@ -77,7 +77,11 @@ set flood.retry.ignore none
|
||||
| `battery.alert.low` | Warning threshold percentage. Must be greater than `battery.alert.critical`. | `get battery.alert.low`, `set battery.alert.low <1-100>` | `set battery.alert.low 20` |
|
||||
| `battery.alert.critical` | Critical threshold percentage. Critical warnings repeat more often. | `get battery.alert.critical`, `set battery.alert.critical <0-99>` | `set battery.alert.critical 10` |
|
||||
| `recent.repeater` | Shows, seeds, or clears the recent repeater prefix/SNR table used by direct retry and bridge freshness checks. | `get recent.repeater`, `get recent.repeater <page>`, `set recent.repeater <prefix> <snr_db>`, `clear recent.repeater` | `set recent.repeater A1B2C3 -8.5` |
|
||||
| `flood.channel.data` | Turns forwarding of flood `GRP_DATA` channel packets on or off, subject to the channel block hop gate. | `get flood.channel.data`, `set flood.channel.data on/off` | `set flood.channel.data off` |
|
||||
| `flood.channel.block` | Blocks selected flood `GRP_TXT`/`GRP_DATA` channels when the key validates the packet. Add `h=<all|1-7|default>` for a per-channel hop override. | `get flood.channel.block`, `set flood.channel.block[.n] <key|#channel> [name] [h=...]`, `del flood.channel.block[.n]` | `set flood.channel.block #wardriving h=3` |
|
||||
| `flood.channel.block.hops` | Limits channel/data forwarding to short flood paths. `all` blocks matching packets at any hop count; `1`-`7` repeats packets at that hop count or lower and blocks longer matches. | `get flood.channel.block.hops`, `set flood.channel.block.hops <all|1-7>` | `set flood.channel.block.hops 3` |
|
||||
| `outpath` | Overrides the primary direct route used for replies to the current remote client. | `get outpath`, `set outpath <hops>`, `set outpath direct`, `set outpath clear`, `set outpath flood` | `set outpath A1B2C3,D4E5F6` |
|
||||
| `altpath` | Adds a secondary direct route for repeater replies to the current remote client. | `get altpath`, `set altpath <hops>`, `set altpath direct`, `set altpath clear`, `set altpath flood` | `set altpath 71CE82,BA09F0` |
|
||||
|
||||
## Other Keymind Commands
|
||||
|
||||
@@ -146,8 +150,8 @@ Serial CLI pages contain up to `128` rows. Remote LoRa CLI pages contain up to
|
||||
|
||||
## Direct Path Overrides
|
||||
|
||||
`outpath` applies to the current remote client ACL entry. It needs remote
|
||||
client context, so it is not useful from the local serial CLI.
|
||||
`outpath` and `altpath` apply to the current remote client ACL entry. They need
|
||||
remote client context, so they are not useful from the local serial CLI.
|
||||
|
||||
Set paths with comma-separated hop hashes. Each hop must be `2`, `4`, or `6`
|
||||
hex characters, and all hops in one path must use the same width.
|
||||
@@ -158,6 +162,9 @@ set outpath A1B2C3,D4E5F6
|
||||
set outpath direct
|
||||
set outpath clear
|
||||
set outpath flood
|
||||
get altpath
|
||||
set altpath 71CE82,BA09F0
|
||||
set altpath clear
|
||||
```
|
||||
|
||||
`set outpath direct` sets a zero-hop direct route for a client reachable without
|
||||
@@ -165,6 +172,14 @@ repeaters. `set outpath clear` forgets the override and lets normal path
|
||||
discovery fill it again. `set outpath flood` forces replies to use flood packets
|
||||
until the client logs in again.
|
||||
|
||||
When `outpath` is a valid direct path and `altpath` is also a valid, different
|
||||
direct path, repeater DM replies send two packets: one on `outpath` and one on
|
||||
`altpath`. The secondary `altpath` copy does not create its own direct-retry
|
||||
state, so retry tracking stays attached to the primary `outpath` packet.
|
||||
`altpath clear` disables the secondary direct reply. `altpath flood` is accepted
|
||||
for command symmetry, but it does not create a second flood reply; only a valid
|
||||
direct `altpath` sends the second packet.
|
||||
|
||||
## Direct Retry Settings
|
||||
|
||||
Direct retry applies to direct-routed packets. A queued resend is canceled when the next-hop echo is heard.
|
||||
|
||||
Reference in new issue
Block a user