adam/meshing-around
1
0 Fork 0
mirror of https://github.com/SpudGunMan/meshing-around.git synced 2026-10-30 22:01:57 +01:00
Code Issues 12 Packages Projects Releases Wiki Activity

relay node in ping #122

New Issue
Open
opened 2026-10-05 01:24:40 +02:00 by adam · 2 comments
adam commented 2026-10-05 01:24:40 +02:00
Owner
Copy link
Copy source

Is it possible to add configurable disaplay of the relay node for the ping answer?
Right now its 2 last symbols of the node id, how about more symbold or even short/long names?

Is it possible to add configurable disaplay of the relay node for the ping answer? Right now its 2 last symbols of the node id, how about more symbold or even short/long names? <!-- github-sync-id:3772244280 -->
adam commented 2026-10-05 01:24:41 +02:00
Author
Owner
Copy link
Copy source

It's a very new feature in meshtastic (the relay)

Some discussions on the discord the other day about this.

Currently it's limited to this data, any duplicate and it could be wrong. In a mesh of 40 nodes for example it's not impossible two have the same last two numbers of the ID the same digits.

I also didn't want to give away any secrets if there was relay nodes which are hidden in anyway. And didn't want to cause a leak with ping

The best way to use the data is search your own node db for the value and you can assume best effort given its location or what not to the bot node.

To some degree it's useless .. but it's there and could be handy in network troubleshooting so I added it.

The story of it and how it got here today.

It's a very new feature in meshtastic (the relay) Some discussions on the discord the other day about this. Currently it's limited to this data, any duplicate and it could be wrong. In a mesh of 40 nodes for example it's not impossible two have the same last two numbers of the ID the same digits. I also didn't want to give away any secrets if there was relay nodes which are hidden in anyway. And didn't want to cause a leak with ping The best way to use the data is search your own node db for the value and you can assume best effort given its location or what not to the bot node. To some degree it's useless .. but it's there and could be handy in network troubleshooting so I added it. The story of it and how it got here today. <!-- github-comment-id:3702662943 -->
adam commented 2026-10-05 01:24:41 +02:00
Author
Owner
Copy link
Copy source

Currently it's limited to this data, any duplicate and it could be wrong. In a mesh of 40 nodes for example it's not impossible two have the same last two numbers of the ID the same digits.

In theory it could be useful to us OR like Node1 OR Node2

> Currently it's limited to this data, any duplicate and it could be wrong. In a mesh of 40 nodes for example it's not impossible two have the same last two numbers of the ID the same digits. In theory it could be useful to us OR like Node1 OR Node2 <!-- github-comment-id:3704065693 -->
adam changed title from relay node in ping to relay node in ping 2026-10-27 11:49:28 +01:00
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/meshing-around#122