diff options
| author | Nobuhiro MIKI <nob@bobuhiro11.net> | 2025-01-29 04:31:53 +0000 |
|---|---|---|
| committer | Mergify <37929162+mergify[bot]@users.noreply.github.com> | 2025-01-29 12:06:15 +0000 |
| commit | 06ce47558ffea3787b093cf7bbabf96d90063e9c (patch) | |
| tree | f64a8450040b07777e8f575284f47611e7f4dd9e /pimd/pim_errors.c | |
| parent | 75991d68a1a7a1db51a14768c112a9b94d2f3d6f (diff) | |
tools: Fix frr-reload for ebgp-multihop TTL reconfiguration.
In ebgp-multihop, there is a difference in reload behavior when TTL is
unspecified (meaning default 255) and when 255 is explicitly specified.
For example, when reloading with 'neighbor <neighbor> ebgp-multihop
255' in the config, the following difference is created. This commit
fixes that.
Lines To Delete
===============
router bgp 65001
no neighbor 10.0.0.4 ebgp-multihop
exit
Lines To Add
============
router bgp 65001
neighbor 10.0.0.4 ebgp-multihop 255
exit
The commit 767aaa3a8048 is not sufficient and frr-reload needs to be
fixed to handle both unspecified and specified cases.
Signed-off-by: Nobuhiro MIKI <nob@bobuhiro11.net>
(cherry picked from commit 594e917656da5502b302309aed3cf596df24713f)
Diffstat (limited to 'pimd/pim_errors.c')
0 files changed, 0 insertions, 0 deletions