summaryrefslogtreecommitdiff
path: root/bgpd/bgp_nht.h
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@nvidia.com>2021-04-12 14:16:30 -0400
committerDonald Sharp <sharpd@nvidia.com>2021-04-15 13:16:28 -0400
commit996319e63d97f156ab538107275143a527949a3c (patch)
tree8975f5afaf36d815cb19921345d535e88ea77fc9 /bgpd/bgp_nht.h
parent0575d5a8f81b6183e3b12454767869952051eaa8 (diff)
bgpd: Address LL peer not NHT when receiving connection attempt
The new LL code in: 8761cd6ddb5437767625f58c8e9cc3ccda7887ab Introduced the idea of the bgp unnumbered peers using interface up/down events to track the bgp peers nexthop. This code was not properly working when a connection was received from a peer in some circumstances. Effectively the connection from a peer was immediately skipping state transitions and FRR was never properly tracking the peers nexthop. When we receive the connection attempt, let's track the nexthop now. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'bgpd/bgp_nht.h')
-rw-r--r--bgpd/bgp_nht.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/bgpd/bgp_nht.h b/bgpd/bgp_nht.h
index a1683e1511..9268b225ca 100644
--- a/bgpd/bgp_nht.h
+++ b/bgpd/bgp_nht.h
@@ -51,7 +51,7 @@ extern int bgp_find_or_add_nexthop(struct bgp *bgp_route,
*/
extern void bgp_unlink_nexthop(struct bgp_path_info *p);
void bgp_unlink_nexthop_by_peer(struct peer *peer);
-
+void bgp_replace_nexthop_by_peer(struct peer *from, struct peer *to);
/**
* bgp_delete_connected_nexthop() - Reset the 'peer' pointer for a connected
* nexthop entry. If no paths reference the nexthop, it will be unregistered