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>
This commit is contained in:
Igor Ryzhov 2021-03-10 01:35:55 +03:00
parent 5aeb216ea5
commit f1825d571e
2 changed files with 6 additions and 1 deletions

View File

@ -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);

View File

@ -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.