From a88be399398d7d394d5692452e864414248fb7a8 Mon Sep 17 00:00:00 2001 From: Trey Aspelund Date: Fri, 8 Nov 2019 16:51:36 -0500 Subject: [PATCH] staticd: Make blackhole keyword errors more straightforward Previous error was misleading and made it seem like Null0, reject, or blackhole nexthops on static routes are invalid. This commit makes it more clear as to why the error is seen. Signed-off-by: Trey Aspelund --- staticd/static_vty.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/staticd/static_vty.c b/staticd/static_vty.c index 8cc4ccced1..48ad10e90c 100644 --- a/staticd/static_vty.c +++ b/staticd/static_vty.c @@ -431,10 +431,10 @@ static int static_route_leak( || strcasecmp(ifname, "blackhole") == 0) { if (vty) vty_out(vty, - "%% Nexthop interface cannot be Null0, reject or blackhole\n"); + "%% Nexthop interface name can not be from reserved keywords (Null0, reject, blackhole)\n"); else zlog_warn( - "%s: Nexthop interface cannot be Null0, reject or blackhole for %s", + "%s: %s: Nexthop interface name can not be from reserved keywords (Null0, reject, blackhole)\n", __PRETTY_FUNCTION__, dest_str); return CMD_WARNING_CONFIG_FAILED; } -- 2.39.5