From fcda45a3cc5f559477a037fd504f54b8d63b5663 Mon Sep 17 00:00:00 2001
From: Kevin Hester <kevinh@geeksville.com>
Date: Sun, 7 Feb 2021 09:45:08 +0800
Subject: [PATCH] add NO_INTERFACE error reason in support of
 https://github.com/meshtastic/Meshtastic-device/issues/677

---
 mesh.proto | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/mesh.proto b/mesh.proto
index 68a05c2..eead5ab 100644
--- a/mesh.proto
+++ b/mesh.proto
@@ -136,8 +136,9 @@ message RouteDiscovery {
   repeated int32 route = 2;
 }
 
-enum RouteError {
+enum ErrorReason {
 
+  /** This message is not a failure */
   NONE = 0;
 
   /*
@@ -151,6 +152,9 @@ enum RouteError {
   GOT_NAK = 2;
 
   TIMEOUT = 3;
+
+  /* No suitable interface could be found for delivering this packet */
+  NO_INTERFACE = 4;
 }
 
 /*
@@ -179,9 +183,10 @@ message SubPacket {
     RouteDiscovery route_reply = 7;
 
     /*
-     * A failure in a routed message
+     * 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).
      */
-    RouteError route_error = 13;
+    ErrorReason error_reason = 13;
 
     /*
      * Prior to 1.20 positions were communicated as a special payload type, now they are GPS_POSITION_APP Data