Admin packet otherwise checks out, but uses a bogus or expired session key
Admin packet sent using PKC, but not from a public key on the admin key list
The application layer service on the remote node received your request, but considered your request somehow invalid
Cannot send currently because duty cycle regulations will be violated.
We received a nak while trying to forward on your behalf
We reached the max retransmission count (typically for naive flood routing)
No suitable channel was found for sending this packet (i.e. was requested channel index disabled?)
No suitable interface could be found for delivering this packet
The request had want_response set, the request reached the destination node, but no service on that node wants to send a response (possibly due to bad channel permissions)
Our node doesn't have a route to the requested destination anymore.
This message is not a failure
The application layer service on the remote node received your request, but considered your request not authorized (i.e you did not send the request on the required bound channel)
The client specified a PKI transport, but the node was unable to send the packet using PKI (and did not send the message at all)
The receiving node does not have a Public Key to decode with
TODO: REPLACE
The packet was too big for sending (exceeds interface MTU after encoding)
A failure in delivering a message (usually used for routing control messages, but might be provided in addition to ack.fail_id to provide details on the type of failure).
Generated
from enum meshtastic.Routing.Error