twisla/roro9stack
Public Access
1
0
Fork 0
Code Issues 34 Pull Requests Actions Packages Releases 27 Activity

LoRa Scanner: MeshCore searches for nodes and their answers, read

Browse Source 
The first two MeshCore packets heard were these: a search for repeaters
and a repeater answering. Both are in clear; they are the test's bytes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0162FokPdvY2KsS4NBfwyWPk
This commit is contained in:
twisla
2026-10-09 20:51:15 +02:00
co-authored by Claude Opus 5.5
parent 8ba41f72b6
commit 3339d9ee59
6 changed files with 97 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
site/content/guide/lora-scanner.md
+4 -1
View File
@@ -20,7 +20,9 @@ For a **MeshCore** packet it shows what the packet is, who it concerns and how m
| `adv Brussels-R1 2h` | A node saying who it is, by its name, heard through 2 repeaters |
| `txt a3>7f` | A private message from the node whose key starts with `a3` to the one starting with `7f` (`req`, `rsp` and `path` look the same) |
| `chan #11 1h` | A message on a channel; `#11` is the channel's byte, and `11` is the public channel's |
| `ack`, `anon`, `trace`, `ctl` | An acknowledgement, a login, a trace, a discovery |
| `who's there?` | Someone nearby searching for nodes (repeaters, usually) |
| `here 18a6` | A node answering that search; `18a6` starts its key |
| `ack`, `anon`, `trace`, `ctl` | An acknowledgement, a login, a trace, other control packets |
| Key | Does |
|---|---|
@@ -42,6 +44,7 @@ The **MeshCore** preset is the setting its networks use in Europe, "EU/UK (Narro
- what it is and how it travels: **flood** (every repeater passes it on, and adds itself to the path) or **direct** (it carries the route to follow);
- the path, one repeater a hop, each named by the first byte of its key;
- for an **advert**, which is signed and never encrypted: the node's name, its kind (chat node, repeater, room server, sensor), the start of its key, and its position if it gives one;
- for a **search** and its **answers**, also in clear: what kind of node is wanted; and in an answer the node's kind, the start of its key, and how well it heard the search;
- for a message: the first byte of the sender's and the receiver's keys, or the channel's byte, and how many bytes are encrypted.
A byte is all a packet says about who it is from: two nodes can share it. The name comes only with a node's advert, which a node sends now and then, so a quiet network can take a while to show its names.