F38-MT: Yes
Rationale
Each node enforces local packet-access decisions through its ignore policy, and its transmission queue orders packets by local priority and can evict lower-priority entries when full. Local clients can supply priority; unset values are assigned by local firmware. Operators can apply their own access policies while interoperating with neighboring nodes.
Assessment method
Pinned firmware schema, queue and router source review
Source context
Meshtastic firmware 8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c
Outstanding qualification
Native node/radio scope, not recursively nested domains or negotiated end-to-end bandwidth. Compatible radio settings and trust provisioning remain required. A local priority value is not propagated as a binding policy for other relays. Ignoring a sender prevents local handling, not reception energy consumption or RF interference.
Public sources
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/MeshPacketQueue.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/Router.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/MeshPacketQueue.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/generated/meshtastic/mesh.pb.h
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round687.html