summaryrefslogtreecommitdiffstats
path: root/bgpd
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@nvidia.com>2021-09-16 14:00:44 +0200
committerDonald Sharp <sharpd@nvidia.com>2021-09-16 14:07:45 +0200
commitdcd5ba55058fc42c592f6c40ad0815aa20f0cbbf (patch)
treee98f2c02eb5a7d2e5e862ae60fb6c2818cded6c0 /bgpd
parentMerge pull request #9596 from LabNConsulting/ziemba/printfrr-nexthop (diff)
downloadfrr-dcd5ba55058fc42c592f6c40ad0815aa20f0cbbf.tar.xz
frr-dcd5ba55058fc42c592f6c40ad0815aa20f0cbbf.zip
bgpd: Allow v6 LL peers to work when connected to as well
Initial commit: 8761cd6ddb5437767625f58c8e9cc3ccda7887ab introduced the idea of v6 LL using interface up/down events instead of nexthop resolution to know when a peering should happen or not. This above commit left a hole where if the remote peer connected to this bgp, the bgp code would still believe the peering is down. Modify the code to double check and ensure that we have proper v6 LL resolution flags set. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'bgpd')
-rw-r--r--bgpd/bgp_network.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/bgpd/bgp_network.c b/bgpd/bgp_network.c
index f72f44f8a..09abb6996 100644
--- a/bgpd/bgp_network.c
+++ b/bgpd/bgp_network.c
@@ -46,6 +46,7 @@
#include "bgpd/bgp_errors.h"
#include "bgpd/bgp_network.h"
#include "bgpd/bgp_zebra.h"
+#include "bgpd/bgp_nht.h"
extern struct zebra_privs_t bgpd_privs;
@@ -603,6 +604,12 @@ static int bgp_accept(struct thread *thread)
BGP_EVENT_ADD(peer, TCP_connection_open);
}
+ /*
+ * If we are doing nht for a peer that is v6 LL based
+ * massage the event system to make things happy
+ */
+ bgp_nht_interface_events(peer);
+
return 0;
}