adam/contact
1
0 Fork 0
mirror of https://github.com/pdxlocations/contact.git synced 2026-10-31 00:01:57 +01:00
Code Issues 16 Packages Projects Releases Wiki Activity

Feature Request: Add TraceRoute functionality #6

New Issue
Closed
opened 2026-10-05 03:15:45 +02:00 by adam · 1 comment
adam commented 2026-10-05 03:15:45 +02:00
Owner
Copy link
Copy source

A feature I commonly use on the Web Client when I am remotely accessing a node over TCP is TraceRoute. It is a useful tool to use when trying to figure out how the mesh is actually routing the messages and packets. This feature is currently not implemented in the meshtastic-curses-client.

I have not given a lot of thought as to how to implement the feature.
It could be a separate text box with it's own input and display box.
Or ...
It could be treated as a special case of a message, in which case a special symbol or string is sent as the client currently inputs a message, the input processing recognizes this special symbol or string, perhaps "<>" or "<~>" and sends a trace route request instead of a message. The returned route information could be displayed as the client displays a message, just with a prepend, prefix, and/or a unique color so the user knew it was a trace route result, and not a regular message.

A feature I commonly use on the Web Client when I am remotely accessing a node over TCP is TraceRoute. It is a useful tool to use when trying to figure out how the mesh is actually routing the messages and packets. This feature is currently not implemented in the meshtastic-curses-client. I have not given a lot of thought as to how to implement the feature. It could be a separate text box with it's own input and display box. Or ... It could be treated as a special case of a message, in which case a special symbol or string is sent as the client currently inputs a message, the input processing recognizes this special symbol or string, perhaps "<>" or "<~>" and sends a trace route request instead of a message. The returned route information could be displayed as the client displays a message, just with a prepend, prefix, and/or a unique color so the user knew it was a trace route result, and not a regular message. <!-- github-sync-id:2476666524 -->
adam closed this issue 2026-10-05 03:15:45 +02:00
adam commented 2026-10-05 03:15:46 +02:00
Author
Owner
Copy link
Copy source

Thanks for adding this feature request. I have most the the "plumbing" already implemented in my MQTT client so it shouldn't be too tricky:
https://github.com/pdxlocations/Meshtastic-MQTT-Connect/blob/f10b5a36229106bcd2d2fb0b45885e699a0eb807/meshtastic-mqtt-connect.py#L671

For the curses client I'm thinking since it's only used when selecting a node I could have a special character or function key used to initiate the traceroute.

Thanks for adding this feature request. I have most the the "plumbing" already implemented in my MQTT client so it shouldn't be too tricky: https://github.com/pdxlocations/Meshtastic-MQTT-Connect/blob/f10b5a36229106bcd2d2fb0b45885e699a0eb807/meshtastic-mqtt-connect.py#L671 For the curses client I'm thinking since it's only used when selecting a node I could have a special character or function key used to initiate the traceroute. <!-- github-comment-id:2299898391 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/contact#6