Back to matrix

F39-MT: Yes

Rationale

Router.sendLocal checks the destination node number: a local destination goes to deliverLocal, while a remote destination goes to send and the radio interface. MeshModule.callModules dispatches the received packet to the selected application port. With native meshtasticd, a separate local client reaches the daemon-hosted service or a remote node service through the same Client API and node/port reference.

Assessment method

Pinned native daemon entry point, API server, local/radio dispatch and module port delivery

Source context

Meshtastic native meshtasticd; Router.sendLocal; MeshModule.callModules; ServerAPI; NodeInfoModule

Outstanding qualification

Source-based Yes for a client process communicating with a service hosted inside the native daemon. This is not arbitrary OS-process registration or a guarantee of multiple concurrent external clients; the API server documents a single active TCP connection. Module callbacks are not counted as separate processes. The local API is trusted and does not imply identical local/remote cryptographic protection. Keep service policies and throttles; no zero-copy, runtime test or new production qualification of the selected Alpha is claimed.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.