mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-02-02 08:42:11 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Use Tabs for Client Availability

Browse source
This commit is contained in:
GUVWAF 2023-01-05 17:50:01 +01:00
parent e21bcf6b68
commit be01a56617
1 changed files with 40 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

46
docs/configuration/module-config/traceroute.mdx
View file

@ -5,15 +5,42 @@ slug: /settings/moduleconfig/traceroute
sidebar_label: Traceroute sidebar_label: Traceroute
--- ---
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
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. 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. 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.
In order to use it, you can use either the Python CLI or the Apple apps. Make sure your devices use firmware version 2.0.8 or higher. In order to use it, make sure your devices use firmware version 2.0.8 or higher.
### CLI ## Traceroute Module Client Availability
For usage with the CLI, make sure it is at least version 2.0.6. Then use this command: <Tabs
groupId="settings"
defaultValue="cli"
values={[
{label: 'Android', value: 'android'},
{label: 'Apple', value: 'apple'},
{label: 'CLI', value: 'cli'},
{label: 'Flasher', value: 'flasher'},
{label: 'Web', value: 'web'},
]}>
<TabItem value="android">
Not yet implemented.
</TabItem>
<TabItem value="apple">
Make sure the app is at least version 2.0.9.
Under Contacts > Direct Messages, long hold a destination node and select 'Trace Route' to send the request. Depending on the amount of hops that is needed, this might take a while. The result will be shown in the Mesh Log.
</TabItem>
<TabItem value="cli">
Make sure the CLI is at least version 2.0.6. Then use this command:
```shell title="CLI traceroute command" ```shell title="CLI traceroute command"
meshtastic --traceroute 'destinationId' meshtastic --traceroute 'destinationId'
@ -31,8 +58,15 @@ Route traced:
The first ID shown is the device you are connected to with the CLI. As you can see, this packet went through one other node to get to its destination. The first ID shown is the device you are connected to with the CLI. As you can see, this packet went through one other node to get to its destination.
### Apple </TabItem>
<TabItem value="flasher">
Make sure the app is at least version 2.0.9. Not implemented.
Under Contacts > Direct Messages, long hold a destination node and select 'Trace Route' to send the request. Depending on the amount of hops that is needed, this might take a while. The result will be shown in the Mesh Log. </TabItem>
<TabItem value="web">
Not yet implemented.
</TabItem>
</Tabs>