summaryrefslogtreecommitdiff
path: root/bgpd
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2016-11-16 12:00:40 -0500
committerDonald Sharp <sharpd@cumulusnetworks.com>2017-05-16 15:21:25 -0400
commit71ffee748f3a5466dc3e73e9f5fb5b286ff3b6c5 (patch)
tree05eadb7737a8e4ed54c6563ed3f6d078954c3e85 /bgpd
parent70a4754dd0eec88e0294c645d7c93d08e4356dda (diff)
bgpd: More Extended nexthop fixing
Basically if we are reading in a cli with a extended-nexthop and we have not received from zebra the interface we are working on I believe we have a race condition where we are not propagating the PEER_FLAG_CAPABILITY_ENHE in this case. Modify the code to propagate even if we haven't found the interface yet. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'bgpd')
-rw-r--r--bgpd/bgpd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/bgpd/bgpd.c b/bgpd/bgpd.c
index 86133cd763..c6997a9b83 100644
--- a/bgpd/bgpd.c
+++ b/bgpd/bgpd.c
@@ -2652,7 +2652,7 @@ peer_group_bind (struct bgp *bgp, union sockunion *su, struct peer *peer,
* Capability extended-nexthop is enabled for an interface neighbor by
* default. So, fix that up here.
*/
- if (peer->ifp && cap_enhe_preset)
+ if (peer->conf_if && cap_enhe_preset)
peer_flag_set (peer, PEER_FLAG_CAPABILITY_ENHE);
for (afi = AFI_IP; afi < AFI_MAX; afi++)