From be01a56617208a6fc09b34a18576f4b4911bde36 Mon Sep 17 00:00:00 2001
From: GUVWAF <thijs@havinga.eu>
Date: Thu, 5 Jan 2023 17:50:01 +0100
Subject: [PATCH] Use Tabs for Client Availability

---
 .../module-config/traceroute.mdx              | 46 ++++++++++++++++---
 1 file changed, 40 insertions(+), 6 deletions(-)

diff --git a/docs/configuration/module-config/traceroute.mdx b/docs/configuration/module-config/traceroute.mdx
index e9227c87..56436298 100644
--- a/docs/configuration/module-config/traceroute.mdx
+++ b/docs/configuration/module-config/traceroute.mdx
@@ -5,15 +5,42 @@ slug: /settings/moduleconfig/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.
 
 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"
 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. 
 
-### 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.
\ No newline at end of file
+</TabItem>
+<TabItem value="web">
+
+Not yet implemented.
+    
+</TabItem>
+</Tabs>
\ No newline at end of file