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 812f35eb89ef26d4c85112a635c2213ea5933dcb..06a90fc1b5f1bc979ff12782a9e8b2693ef390ef 100644 (file)
--- 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;
 }