summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIgor Ryzhov <iryzhov@nfware.com>2021-03-10 01:35:55 +0300
committerIgor Ryzhov <iryzhov@nfware.com>2021-03-16 17:25:06 +0300
commitf1825d571e2cf48922fe86d5158018a13bd75d4c (patch)
tree2f1c612eb700598304d019d04de0e57f5693e2cf
parent5aeb216ea53f330a3ac72e3982dcff9500bc1fb3 (diff)
bfdd: warn users about echo-mode restrictions
Echo-mode implementation is currently broken. Instead of sending packets to it's own address, bfdd is sending echo packets to the peer's address. It may seem to work when testing between two FRR instances, because FRR loops back such packets, but no other implementation is supposed to do that. Let's warn users that the current implementation works only between two FRR instances. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
-rw-r--r--bfdd/bfdd_cli.c4
-rw-r--r--doc/user/bfd.rst3
2 files changed, 6 insertions, 1 deletions
diff --git a/bfdd/bfdd_cli.c b/bfdd/bfdd_cli.c
index 206f6c7d0c..211588cce1 100644
--- a/bfdd/bfdd_cli.c
+++ b/bfdd/bfdd_cli.c
@@ -433,6 +433,10 @@ DEFPY_YANG(
return CMD_WARNING_CONFIG_FAILED;
}
+ if (!no && !bglobal.bg_use_dplane) {
+ vty_out(vty, "%% Current implementation of echo mode works only when the peer is also FRR.\n");
+ }
+
nb_cli_enqueue_change(vty, "./echo-mode", NB_OP_MODIFY,
no ? "false" : "true");
return nb_cli_apply_changes(vty, NULL);
diff --git a/doc/user/bfd.rst b/doc/user/bfd.rst
index b8f749b740..87f560b5bb 100644
--- a/doc/user/bfd.rst
+++ b/doc/user/bfd.rst
@@ -174,7 +174,8 @@ BFD peers and profiles share the same BFD session configuration commands.
.. clicmd:: echo-mode
Enables or disables the echo transmission mode. This mode is disabled
- by default.
+ by default. If you are not using distributed BFD then echo mode works
+ only when the peer is also FRR.
It is recommended that the transmission interval of control packets
to be increased after enabling echo-mode to reduce bandwidth usage.