From: Donald Sharp <sharpd@cumulusnetworks.com>
Date: Mon, 13 Apr 2020 12:12:26 +0000 (-0400)
Subject: sharpd: Allow sharpd to specify it's own routes for label changes
X-Git-Tag: base_7.4~101^2
X-Git-Url: https://git.puffer.fish/?a=commitdiff_plain;h=4b0f62376cdf0814c8fb689632a6611c73a199ec;p=matthieu%2Ffrr.git

sharpd: Allow sharpd to specify it's own routes for label changes

With the command using STR_SHARP, the sharp daemon is not allowed
to use it's own routes for label modification.  Switching over
to STR_ZEBRA allows the sharp daemon to modify labels on any
route in the system, since there are no `ROUTE_ZEBRA` types.

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
---

diff --git a/sharpd/sharp_vty.c b/sharpd/sharp_vty.c
index 8a787c8e83..e2ea773055 100644
--- a/sharpd/sharp_vty.c
+++ b/sharpd/sharp_vty.c
@@ -397,7 +397,7 @@ DEFPY(sharp_lsp_prefix_v4, sharp_lsp_prefix_v4_cmd,
       "sharp lsp (0-100000)$inlabel\
         nexthop-group NHGNAME$nhgname\
         [prefix A.B.C.D/M$pfx\
-       " FRR_IP_REDIST_STR_SHARPD "$type_str [instance (0-255)$instance]]",
+       " FRR_IP_REDIST_STR_ZEBRA "$type_str [instance (0-255)$instance]]",
       "Sharp Routing Protocol\n"
       "Add an LSP\n"
       "The ingress label to use\n"
@@ -405,7 +405,7 @@ DEFPY(sharp_lsp_prefix_v4, sharp_lsp_prefix_v4_cmd,
       "The nexthop-group name\n"
       "Label a prefix\n"
       "The v4 prefix to label\n"
-      FRR_IP_REDIST_HELP_STR_SHARPD
+      FRR_IP_REDIST_HELP_STR_ZEBRA
       "Instance to use\n"
       "Instance\n")
 {