From: Donatas Abraitis <donatas@opensourcerouting.org>
Date: Tue, 12 Mar 2024 19:14:13 +0000 (+0200)
Subject: bgpd: Set Paths Limit to 0 instead of unsetting the capability
X-Git-Tag: base_10.1~245^2~2
X-Git-Url: https://git.puffer.fish/?a=commitdiff_plain;h=56a23f056c6de342a28576c38295542adaa96d84;p=matthieu%2Ffrr.git

bgpd: Set Paths Limit to 0 instead of unsetting the capability

The capability should be untouched, and send 0 (unlimited) instead.

Otherwise, we miss the capability and things are broken later until the
session reset.

Fixes: 72f0e06824c237238121b96c45845a57e5cfb59f ("bgpd: Implement Paths-Limit capability")

Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
---

diff --git a/bgpd/bgp_vty.c b/bgpd/bgp_vty.c
index 812f35eb89..06a90fc1b5 100644
--- a/bgpd/bgp_vty.c
+++ b/bgpd/bgp_vty.c
@@ -9261,7 +9261,7 @@ DEFPY (no_neighbor_addpath_paths_limit,
 	peer->addpath_paths_limit[afi][safi].send = 0;
 
 	bgp_capability_send(peer, afi, safi, CAPABILITY_CODE_PATHS_LIMIT,
-			    CAPABILITY_ACTION_UNSET);
+			    CAPABILITY_ACTION_SET);
 
 	return ret;
 }