matthieu/frr
1
0
Fork 0
forked from Mirror/frr
Code Pull requests Activity
frr/bgpd/bgp_zebra.h

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

123 lines
5.2 KiB
C
Raw Normal View History

*: auto-convert to SPDX License IDs Done with a combination of regex'ing and banging my head against a wall. Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
2023-02-08 13:17:09 +01:00
// SPDX-License-Identifier: GPL-2.0-or-later
Initial revision
2002-12-13 21:15:29 +01:00
/* zebra connection and redistribute fucntions.
*: make consistent & update GPLv2 file headers The FSF's address changed, and we had a mixture of comment styles for the GPL file header. (The style with * at the beginning won out with 580 to 141 in existing files.) Note: I've intentionally left intact other "variations" of the copyright header, e.g. whether it says "Zebra", "Quagga", "FRR", or nothing. Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
2017-05-13 10:25:29 +02:00
* Copyright (C) 1999 Kunihiro Ishiguro
*/
Initial revision
2002-12-13 21:15:29 +01:00
2005-05-23 Paul Jakma <paul@dishone.st> * bgp_fsm.h: Add extern qualifier to exported functions * bgp_nexthop.c: add static to nexthop specific globals * *.h: Add guard defines
2005-05-23 16:19:54 +02:00
#ifndef _QUAGGA_BGP_ZEBRA_H
#define _QUAGGA_BGP_ZEBRA_H
bgpd/zebra/lib: EVPN support for asymmetric VxLan routing 1. Advertise gateway mac-ip in EVPN 2. Advertise VRR mac-ip in EVPN 3. Ignore gateway mac-ip advertisements in case of distributed gateway 4. Config knob to enable/disable gateway mac-ip advertisements Ticket: CM-16456, CM-16543, CM-16555, CM-16778 Review: CCR-6283 Unit-test: Manual Signed-off-by: Mitesh Kanjariya <mitesh@cumulusnetworks.com>
2017-06-28 10:51:10 +02:00
#include "vxlan.h"
bgpd: Few code optimisations Description: Added a macro which optimises some part of the code. Co-authored-by: Santosh P K <sapk@vmware.com> Co-authored-by: Kantesh Mundaragi <kmundaragi@vmware.com> Signed-off-by: Iqra Siddiqui <imujeebsiddi@vmware.com>
2021-09-17 17:50:03 +02:00
/* Macro to update bgp_original based on bpg_path_info */
#define BGP_ORIGINAL_UPDATE(_bgp_orig, _mpinfo, _bgp) \
((_mpinfo->extra && _mpinfo->extra->bgp_orig \
&& _mpinfo->sub_type == BGP_ROUTE_IMPORTED) \
? (_bgp_orig = _mpinfo->extra->bgp_orig) \
: (_bgp_orig = _bgp))
bgpd: Implement options for link bandwidth handling Support configurable options to control how link bandwidth is handled by the receiver. The default behavior is to automatically honor the link bandwidths received and use it to perform a weighted ECMP BUT only if all paths in the multipath have associated link bandwidth; if one or more paths do not have link bandwidth, normal ECMP is performed among the multipaths. This behavior is as recommended by https://tools.ietf.org/html/draft-ietf-idr-link-bandwidth. The additional options available are to (a) completely ignore any link bandwidth (i.e., weighted ECMP is effectively disabled), (b) skip paths in the multipath which do not have link bandwidth and perform weighted ECMP among the other paths (if at least some paths have the bandwidth) or (c) use a default weight (value chosen is 1) for the paths which do not have link bandwidth. The command syntax is bgp bestpath bandwidth <ignore|skip-missing|default-weight-for-missing> Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com>
2020-03-24 22:38:37 +01:00
/* Default weight for next hop, if doing weighted ECMP. */
#define BGP_ZEBRA_DEFAULT_NHOP_WEIGHT 1
*: Convert struct thread_master to struct event_master and it's ilk Convert the `struct thread_master` to `struct event_master` across the code base. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-12-11 17:20:40 +01:00
extern void bgp_zebra_init(struct event_master *master,
bgpd, doc, ldpd, lib, tests, zebra: LM fixes Corrections so that the BGP daemon can work with the label manager properly through a label-manager proxy. Details: - Correction so the BGP daemon behind a proxy label manager gets the range correctly (-I added to the BGP daemon, to set the daemon instance id) - For the BGP case, added an asynchronous label manager connect command so the labels get recycled in case of a BGP daemon reconnection. With this, BGPd and LDPd would behave similarly. Signed-off-by: F. Aragon <paco@voltanet.io>
2018-06-07 15:28:12 +02:00
unsigned short instance);
bgpd: add 'mpls bgp forwarding' to ease mpls vpn ebgp peering RFC4364 describes peerings between multiple AS domains, to ease the continuity of VPN services across multiple SPs. This commit implements a sub-set of IETF option b) described in chapter 10 b. The ASBR to ASBR approach is taken, with an EBGP peering between the two routers. The EBGP peering must be directly connected to the outgoing interface used. In those conditions, the next hop is directly connected, and there is no need to have a transport label to convey the VPN label. A new vty command is added on a per interface basis: This command if enabled, will permit to convey BGP VPN labels without any transport labels (i.e. with implicit-null label). restriction: this command is used only for EBGP directly connected peerings. Other use cases are not covered. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2022-08-17 11:52:51 +02:00
extern void bgp_if_init(void);
bgpd: do not install BGP FS entries, while table range not obtained Sometimes at startup, BGP Flowspec may be allocated a routing table identifier not in the range of the predefined table range. This issue is due to the fact that BGP peering goes up, while the BGP did not yet retrieve the Table Range allocator. The fix is done so that BGP PBR entries are not installed while routing table identifier range is not obtained. Once the routing table identifier is obtained, parse the FS entries and check that all selected entries are installed, and if not, install it. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-05-23 14:14:53 +02:00
extern void bgp_zebra_init_tm_connect(struct bgp *bgp);
bgpd: get table identifier from table manager A table chunk of 100000 is allocated from zebra, and when needed in flowspec, the table identifier is extracted from that chunk. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-04-03 15:06:50 +02:00
extern uint32_t bgp_zebra_tm_get_id(void);
bgpd: do not install BGP FS entries, while table range not obtained Sometimes at startup, BGP Flowspec may be allocated a routing table identifier not in the range of the predefined table range. This issue is due to the fact that BGP peering goes up, while the BGP did not yet retrieve the Table Range allocator. The fix is done so that BGP PBR entries are not installed while routing table identifier range is not obtained. Once the routing table identifier is obtained, parse the FS entries and check that all selected entries are installed, and if not, install it. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-05-23 14:14:53 +02:00
extern bool bgp_zebra_tm_chunk_obtained(void);
bgpd: improve cleanup in bgp_delete() Signed-off-by: Lou Berger <lberger@labn.net> (cherry picked from commit 82dd707988b7481e203cab058c92f0b3041dd558) Conflicts: bgpd/bgp_nexthop.h bgpd/bgp_route.c bgpd/bgp_routemap.c bgpd/bgp_zebra.h bgpd/bgpd.c bgpd/bgpd.h
2016-01-12 19:41:57 +01:00
extern void bgp_zebra_destroy(void);
bgpd: add API to allocate a range of table identifiers In BGP, doing policy-routing requires to use table identifiers. Flowspec protocol will need to have that. 1 API from bgp zebra has been done to get the table chunk. Internally, onec flowspec is enabled, the BGP engine will try to connect smoothly to the table manager. If zebra is not connected, it will try to connect 10 seconds later. If zebra is connected, and it is success, then a polling mechanism each 60 seconds is put in place. All the internal mechanism has no impact on the BGP process. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-03-05 18:09:57 +01:00
extern int bgp_zebra_get_table_range(uint32_t chunk_size,
uint32_t *start, uint32_t *end);
2005-06-28 Paul Jakma <paul.jakma@sun.com> * (global) The great bgpd extern and static'ification. * bgp_routemap.c: remove unused ROUTE_MATCH_ASPATH_OLD code (route_set_metric_compile) fix u_int32_t to ULONG_MAX comparison warnings. * bgp_route.h: (bgp_process, bgp_withdraw, bgp_update) export these used by various files which had their own private declarations, in the case of mplsvpn - incorrect.
2005-06-28 14:44:16 +02:00
extern int bgp_if_update_all(void);
bgp: rename bgp_node to bgp_dest This is the bulk part extracted from "bgpd: Convert from `struct bgp_node` to `struct bgp_dest`". It should not result in any functional change. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com> Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
2020-03-27 00:11:58 +01:00
extern void bgp_zebra_announce(struct bgp_dest *dest, const struct prefix *p,
bgpd: Convert `struct bgp_info` to `struct bgp_path_info` Do a straight conversion of `struct bgp_info` to `struct bgp_path_info`. This commit will setup the rename of variables as well. This is being done because `struct bgp_info` is not descriptive of what this data actually is. It is path information for routes that we keep to build the actual routes nexthops plus some extra information. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2018-10-02 22:41:30 +02:00
struct bgp_path_info *path, struct bgp *bgp,
afi_t afi, safi_t safi);
bgpd: Align bgp_zebra.h to our standards bgp_zebra.h has function declarations that are not properly aligned with our standard on how to do so. Fix. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-05-12 14:28:11 +02:00
extern void bgp_zebra_announce_table(struct bgp *bgp, afi_t afi, safi_t safi);
bgpd: Rework code to use `const struct prefix` Future work needs the ability to specify a const struct prefix value. Iterate into bgp a bit to get this started. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2020-03-22 02:56:36 +01:00
extern void bgp_zebra_withdraw(const struct prefix *p,
struct bgp_path_info *path, struct bgp *bgp,
safi_t safi);
*: reindent indent.py `git ls-files | pcregrep '\.[ch]$' | pcregrep -v '^(ldpd|babeld|nhrpd)/'` Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
2017-07-17 14:03:14 +02:00
bgpd: set/unset bgpd no-rib option at runtime * Added vtysh cli commands and functions to set/unset bgp daemons no-rib option during runtime and withdraw/announce routes in bgp instances RIB from/to Zebra. Signed-off-by: David Schweizer <dschweizer@opensourcerouting.org>
2020-09-02 18:20:08 +02:00
/* Announce routes of any bgp subtype of a table to zebra */
extern void bgp_zebra_announce_table_all_subtypes(struct bgp *bgp, afi_t afi,
safi_t safi);
/* Withdraw all entries of any subtype in a BGP instances RIB table from Zebra */
extern void bgp_zebra_withdraw_table_all_subtypes(struct bgp *bgp, afi_t afi,
safi_t safi);
BGP: Trigger IPv6 router advertisements upon config of unnumbered neighbor Instead of turning on IPv6 RA on every interface as soon as it has an IPv6 address, only enable it upon configuration of BGP neighbor. When the BGP neighbor is deleted, signal that RAs can be turned off. To support this, introduce new message interaction between BGP and Zebra. Also, take appropriate actions in BGP upon interface add/del since the unnumbered neighbor could exist prior to interface creation etc. Only unnumbered IPv6 neighbors require RA, the /30 or /31 based neighbors don't. However, to keep the interaction simple and not have to deal with too many dynamic conditions (e.g., address deletes or neighbor change to/from 'v6only'), RAs on the interface are triggered upon any unnumbered neighbor configuration. BGP-triggered RAs will cause RAs to be initiated on the interface; however, if BGP asks that RAs be stopped (upon delete of unnumbered neighbor), RAs will continue to be exchanged if the operator has explicitly enabled. Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com> Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com> Ticket: CM-10640 Reviewed By: CCR-4589 Testing Done: Various manual and automated (refer to defect)
2016-05-02 22:53:38 +02:00
extern void bgp_zebra_initiate_radv(struct bgp *bgp, struct peer *peer);
extern void bgp_zebra_terminate_radv(struct bgp *bgp, struct peer *peer);
*: reindent indent.py `git ls-files | pcregrep '\.[ch]$' | pcregrep -v '^(ldpd|babeld|nhrpd)/'` Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
2017-07-17 14:03:14 +02:00
bgpd: Align bgp_zebra.h to our standards bgp_zebra.h has function declarations that are not properly aligned with our standard on how to do so. Fix. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-05-12 14:28:11 +02:00
extern void bgp_zebra_instance_register(struct bgp *bgp);
extern void bgp_zebra_instance_deregister(struct bgp *bgp);
*: reindent indent.py `git ls-files | pcregrep '\.[ch]$' | pcregrep -v '^(ldpd|babeld|nhrpd)/'` Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
2017-07-17 14:03:14 +02:00
bgpd: move bgp_update_redist_vrf_bitmaps to bgp_zebra.c for wider use beyond bgp_vty Signed-off-by: Don Slice <dslice@cumulusnetworks.com>
2019-03-13 19:41:29 +01:00
extern void bgp_redistribute_redo(struct bgp *bgp);
bgpd: Align bgp_zebra.h to our standards bgp_zebra.h has function declarations that are not properly aligned with our standard on how to do so. Fix. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-05-12 14:28:11 +02:00
extern struct bgp_redist *bgp_redist_lookup(struct bgp *bgp, afi_t afi,
uint8_t type,
unsigned short instance);
extern struct bgp_redist *bgp_redist_add(struct bgp *bgp, afi_t afi,
uint8_t type, unsigned short instance);
extern int bgp_redistribute_set(struct bgp *bgp, afi_t afi, int type,
unsigned short instance, bool changed);
extern int bgp_redistribute_resend(struct bgp *bgp, afi_t afi, int type,
unsigned short instance);
bgpd: Convert lots of int type functions to bool/void Some were converted to bool, where true/false status is needed. Converted to void only those, where the return status was only false or true. Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
2020-03-20 10:57:54 +01:00
extern bool bgp_redistribute_rmap_set(struct bgp_redist *red, const char *name,
struct route_map *route_map);
bgpd: Align bgp_zebra.h to our standards bgp_zebra.h has function declarations that are not properly aligned with our standard on how to do so. Fix. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-05-12 14:28:11 +02:00
extern bool bgp_redistribute_metric_set(struct bgp *bgp, struct bgp_redist *red,
afi_t afi, int type, uint32_t metric);
extern int bgp_redistribute_unset(struct bgp *bgp, afi_t afi, int type,
unsigned short instance);
extern int bgp_redistribute_unreg(struct bgp *bgp, afi_t afi, int type,
unsigned short instance);
*: reindent indent.py `git ls-files | pcregrep '\.[ch]$' | pcregrep -v '^(ldpd|babeld|nhrpd)/'` Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
2017-07-17 14:03:14 +02:00
bgpd: Align bgp_zebra.h to our standards bgp_zebra.h has function declarations that are not properly aligned with our standard on how to do so. Fix. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-05-12 14:28:11 +02:00
extern struct interface *if_lookup_by_ipv4(struct in_addr *addr,
vrf_id_t vrf_id);
extern struct interface *if_lookup_by_ipv4_exact(struct in_addr *addr,
vrf_id_t vrf_id);
extern struct interface *if_lookup_by_ipv6(struct in6_addr *addr,
ifindex_t ifindex, vrf_id_t vrf_id);
extern struct interface *if_lookup_by_ipv6_exact(struct in6_addr *addr,
ifindex_t ifindex,
vrf_id_t vrf_id);
bgpd: advertise VNI subnet In EVPN symmetric routing, not all subnets are presents everywhere. We have multiple scenarios where a host might not get learned locally. 1. GARP miss 2. SVI down/up 3. Silent host We need a mechanism to resolve such hosts. In order to achieve this, we will be advertising a subnet route from a box and that box will help in resolving the ARP to such hosts. Signed-off-by: Mitesh Kanjariya <mitesh@cumulusnetworks.com>
2017-11-20 06:47:04 +01:00
extern int bgp_zebra_advertise_subnet(struct bgp *bgp, int advertise,
vni_t vni);
bgpd: Align bgp_zebra.h to our standards bgp_zebra.h has function declarations that are not properly aligned with our standard on how to do so. Fix. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-05-12 14:28:11 +02:00
extern int bgp_zebra_advertise_gw_macip(struct bgp *bgp, int advertise,
vni_t vni);
bgpd: advertise svi ip as macip zebra parse api Ticket:CM-23782 Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>
2019-02-04 02:29:59 +01:00
extern int bgp_zebra_advertise_svi_macip(struct bgp *bgp, int advertise,
vni_t vni);
bgpd: Align bgp_zebra.h to our standards bgp_zebra.h has function declarations that are not properly aligned with our standard on how to do so. Fix. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-05-12 14:28:11 +02:00
extern int bgp_zebra_advertise_all_vni(struct bgp *bgp, int advertise);
bgpd: dup addr detect config cli Duplicate address detection configuration clis under bgp l2vpn evpn config mode. - Enabled/Disable (global knob) for feature. - Configure cli for duplicate detection action freeze and freze until time (auto-recovery). Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>
2018-11-01 16:28:08 +01:00
extern int bgp_zebra_dup_addr_detection(struct bgp *bgp);
bgpd: Add '[no] flood <disable|head-end-replication>' Add the '[no] flood <disable|head-end-replication>' command to the l2vpn evpn afi/safi sub commands for bgp. This command when entered as 'flood disable' will turn off type 3 route generation for the transmittal of the type 3 route necessary for BUM replication on the remote VTEP. Additionally it will turn off the BUM handling via the new zebra command, ZEBRA_VXLAN_FLOOD_CONTROL. Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com> Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2018-10-05 01:20:12 +02:00
extern int bgp_zebra_vxlan_flood_control(struct bgp *bgp,
enum vxlan_flood_control flood_ctrl);
bgpd: Implement EVPN enable/disable Implement the command 'advertise-all-vni' under the EVPN address-family in order to allow the local system to learn about local VNIs (and MACs and Neighbors corresponding to those VNIs) and exchange with other EVPN speakers. Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com> Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com> Reviewed-by: Dinesh Dutt <ddutt@cumulusnetworks.com>
2017-05-15 23:30:19 +02:00
bgp: ignore NHT when bgpd has never connected to zebra
2016-10-07 15:44:42 +02:00
extern int bgp_zebra_num_connects(void);
bgpd: Align bgp_zebra.h to our standards bgp_zebra.h has function declarations that are not properly aligned with our standard on how to do so. Fix. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-05-12 14:28:11 +02:00
extern bool bgp_zebra_nexthop_set(union sockunion *local,
union sockunion *remote,
struct bgp_nexthop *nexthop,
struct peer *peer);
bgpd: communication with zebra for ipset & iprule handling The APIs that handle ipset and iprule contexts from zebra are being handled in this commit. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-03-08 15:39:19 +01:00
struct bgp_pbr_action;
struct bgp_pbr_match;
bgpd: ip rule zebra layer adapted to handle both cases now, ip rule can be created from two differnt ways; however a single zebra API has been defined. so make it consistent by adding a parameter to the bgp zebra layer. the function will handle the rest. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-11-29 15:14:41 +01:00
struct bgp_pbr_rule;
bgpd: communication with zebra for ipset & iprule handling The APIs that handle ipset and iprule contexts from zebra are being handled in this commit. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-03-08 15:39:19 +01:00
struct bgp_pbr_match_entry;
bgpd: Adding header files for BGPD-ZEBRA integration for GR. Data Structures, function declaration and Macros forSignalling from BGPD to ZEBRA to enable or disable GR feature in ZEBRA depending on bgp per peer gr configuration. Signed-off-by: Biswajit Sadhu <sadhub@vmware.com>
2019-10-25 17:42:39 +02:00
bgpd: communication with zebra for ipset & iprule handling The APIs that handle ipset and iprule contexts from zebra are being handled in this commit. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-03-08 15:39:19 +01:00
extern void bgp_send_pbr_rule_action(struct bgp_pbr_action *pbra,
bgpd: ip rule zebra layer adapted to handle both cases now, ip rule can be created from two differnt ways; however a single zebra API has been defined. so make it consistent by adding a parameter to the bgp zebra layer. the function will handle the rest. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-11-29 15:14:41 +01:00
struct bgp_pbr_rule *pbr,
bool install);
bgpd: communication with zebra for ipset & iprule handling The APIs that handle ipset and iprule contexts from zebra are being handled in this commit. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-03-08 15:39:19 +01:00
extern void bgp_send_pbr_ipset_match(struct bgp_pbr_match *pbrim,
bool install);
extern void bgp_send_pbr_ipset_entry_match(struct bgp_pbr_match_entry *pbrime,
bool install);
bgpd: handle configuration of iptables with zebra The API for filling in an IPTABLE_ADD and IPTABLE_DELETE message. Also, the API is handling the notification callback, so as to know if zebra managed to add or delete the relevant iptable entry. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-03-12 09:38:53 +01:00
extern void bgp_send_pbr_iptable(struct bgp_pbr_action *pba,
struct bgp_pbr_match *pbm,
bool install);
bgpd: communication with zebra for ipset & iprule handling The APIs that handle ipset and iprule contexts from zebra are being handled in this commit. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-03-08 15:39:19 +01:00
bgpd: handle FS redirect IP rule in PBR If a new rule is identified, a new table identifier is created. In that table, add a default route when possible. If redirect IP rule is identified, then add a default route to that IP address. If redirect VRF is identified, nothing is done for now Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
2018-03-28 14:51:57 +02:00
extern void bgp_zebra_announce_default(struct bgp *bgp, struct nexthop *nh,
afi_t afi, uint32_t table_id, bool announce);
bgpd: Adding header files for BGPD-ZEBRA integration for GR. Data Structures, function declaration and Macros forSignalling from BGPD to ZEBRA to enable or disable GR feature in ZEBRA depending on bgp per peer gr configuration. Signed-off-by: Biswajit Sadhu <sadhub@vmware.com>
2019-10-25 17:42:39 +02:00
extern int bgp_zebra_send_capabilities(struct bgp *bgp, bool disable);
lib, bgpd: Add more debugs to GR Capability exchange a) Make it legible what type of message is being passed back and forth instead of having to guess it from the insufficient debugs b) Make it explicit which bgp instance is sending this data c) Cleanup bgp_zebra_update to have a cleaner api Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2023-03-09 14:36:51 +01:00
extern int bgp_zebra_update(struct bgp *bgp, afi_t afi, safi_t safi,
enum zserv_client_capabilities);
bgpd: Adding header files for BGPD-ZEBRA integration for GR. Data Structures, function declaration and Macros forSignalling from BGPD to ZEBRA to enable or disable GR feature in ZEBRA depending on bgp per peer gr configuration. Signed-off-by: Biswajit Sadhu <sadhub@vmware.com>
2019-10-25 17:42:39 +02:00
extern int bgp_zebra_stale_timer_update(struct bgp *bgp);
bgpd: cli for srv6-locator assignment (step4) This commit add command to speficy SRv6 locator for BGP SRv6-VPN. CLI example is follow. CLI block of "segment-routing" is already implemented by previous commits and it's managed by zebra. Zebra manage just the ownership of locator's prefix. Zlient can request to get srv6-locator's prefix chunk using srv6_manager_get_locator_chunk() which is usuful func to execute ZEBRA_SRV6_MANAGER_GET_LOCATOR_CHUNK api. This request is wokring as async, And zebra calls same api to Zclients when zebra allocate locator prefix chunk. And then, finally zclient(bgpd) catch the information via process_srv6_lcoator_chunk callback function. router bgp 1 segment-routing srv6 locator loc1 ! ! segment-routing srv6 locators locator loc1 prefix 2001:db8:1:1::/64 ! ! ! ! [POINT_OF_REVIEW] In current implementation, user can just configure srv6 locator but user can't de-configure srv6 locator. Signed-off-by: Hiroki Shirokura <slank.dev@gmail.com>
2020-12-19 02:50:18 +01:00
extern int bgp_zebra_srv6_manager_get_locator_chunk(const char *name);
bgpd: add no-cli for srv6 on bgpd-side (1) Implement zapi wrapper func to release srv6-locator-chunk (2) Implement no locator NAME command router bgp 1 segment-routing srv6 no locator loc1 (3) Implement no segment-routing srv6 command router bgp 1 no segment-routing srv6 Signed-off-by: Hiroki Shirokura <slank.dev@gmail.com>
2021-09-14 00:11:11 +02:00
extern int bgp_zebra_srv6_manager_release_locator_chunk(const char *name);
2005-05-23 Paul Jakma <paul@dishone.st> * bgp_fsm.h: Add extern qualifier to exported functions * bgp_nexthop.c: add static to nexthop specific globals * *.h: Add guard defines
2005-05-23 16:19:54 +02:00
#endif /* _QUAGGA_BGP_ZEBRA_H */
Copy permalink