Node identity: announce this Node, and answer requests #33

Open
opened 2026-10-05 20:07:20 +00:00 by twisla · 0 comments
Owner

What

Make this device a Node others can see: its node number, its long and short names, sent as node info now and then, and in answer to a Node that asks.

What's known

  • The names exist since M0's Setup wizard (Settings: LongName, ShortName); the node number comes from the chip's MAC address, as Meshtastic does it.
  • Meshtastic Nodes broadcast their node info periodically and on request (want_response). A reply from a neighbour to ours is a first proof that our transmissions are understood.
  • Node info carries the hardware model and the role (Client).
  • With public-key Direct Messages, node info is also where the public key travels (#30, question 4).

Questions

  1. How often, within the Duty Cycle Budget?
  2. Which hardware model do we announce: Meshtastic's value for the Cardputer ADV, or "private"?
  3. Do we answer other requests (position, traceroute, telemetry)?

Related

src/platform/identity.h, lib/services/src/settings.h, #31, #32, #30.

## What Make this device a Node others can see: its node number, its long and short names, sent as node info now and then, and in answer to a Node that asks. ## What's known - The names exist since M0's Setup wizard (Settings: LongName, ShortName); the node number comes from the chip's MAC address, as Meshtastic does it. - Meshtastic Nodes broadcast their node info periodically and on request (`want_response`). A reply from a neighbour to ours is a first proof that our transmissions are understood. - Node info carries the hardware model and the role (Client). - With public-key Direct Messages, node info is also where the public key travels (#30, question 4). ## Questions 1. How often, within the Duty Cycle Budget? 2. Which hardware model do we announce: Meshtastic's value for the Cardputer ADV, or "private"? 3. Do we answer other requests (position, traceroute, telemetry)? ## Related `src/platform/identity.h`, `lib/services/src/settings.h`, #31, #32, #30.
twisla added this to the M5 Mesh transmit milestone 2026-10-05 20:07:20 +00:00
twisla added the
kind
feature
area/lora
status
blocked
priority
medium
labels 2026-10-05 20:07:20 +00:00
twisla added a new dependency 2026-10-05 20:07:20 +00:00
twisla added a new dependency 2026-10-05 20:07:20 +00:00
twisla added a new dependency 2026-10-05 20:07:22 +00:00
twisla added a new dependency 2026-10-05 20:07:23 +00:00
twisla added a new dependency 2026-10-05 20:07:24 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: twisla/roro9stack#33