mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-01-29 14:51:50 -08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

document repeater role behavior

Browse source
This commit is contained in:
rcarteraz 2024-03-11 07:40:39 -07:00 committed by GitHub
parent a5bb1f916f
commit 76422521de
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/configuration/module/traceroute.mdx
View file

@ -7,6 +7,9 @@ sidebar_label: Traceroute
import Tabs from "@theme/Tabs";
import TabItem from "@theme/TabItem";
## Overview
Due to the limited bandwidth of LoRa, Meshtastic does not keep track of the nodes a message used to hop to the destination. However, from firmware 2.0.8 on, there is a Traceroute Module that can show you this.
Only nodes that know the encryption key of the channel you use can be tracked. Also note that a message may arrive via multiple routes due to duplication because of rebroadcasting. This module will only track the hops of the first packet containing the traceroute request that arrived at the destination.
@ -15,6 +18,10 @@ In order to use it, make sure your devices use firmware version 2.0.8 or higher.
<object data="https://www.youtube.com/embed/PKUmaELKaUo?autohide=1&autoplay=0" width="100%" height="400"></object>
## Repeater Behavior
Repeater nodes will appear in the traceroute log if they have the encryption key, but if they are not in the node list they might appear as "Unknown" depending on the app.
## Traceroute Module Client Availability
<Tabs