matthieu/frr
1
0
Fork 0
forked from Mirror/frr
Code Pull requests Activity
frr/zebra/redistribute.h

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

77 lines
2.6 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
/*
* Redistribution Handler
* Copyright (C) 1999 Kunihiro Ishiguro
*/
#ifndef _ZEBRA_REDISTRIBUTE_H
#define _ZEBRA_REDISTRIBUTE_H
#include "table.h"
zebra-redistribute-table.patch Zebra: Redistribute routes from non-main kernel table to main. This can be the basis for many interesting features such as variations of redistribute ARP, using zebra as the RIB in the presence of multiple routing protocol stacks etc. The code only supports IPv4 for now, but the infrastructure is in place for IPv6. Usage: There is a new route type introduced by this model: TABLE. Routes imported from alternate kernel tables will have their protocol type set to TABLE. Routes from alternate kernel tables MUST be first imported into the main table via "ip import-table <table id>". They can then be redistributed via a routing protocol via the "redistribute table" command. Each imported table can an optional administrative distance specified. In Zebra, a route with a lower distance is chosen over routes with a higher distance. So, distance is how the user can choose to prioritize routes from a particular table over routes from other tables or routes learnt another way in zebra. Route maps for imported tables are specified via "ip protocol" command in zebra. Route maps for redistributed routes within a routing protocol are subject to the route map options supported by the protocol. The "match source-protocol" option in route maps can match against "table" to filter routes learnt from alternate kernel routing tables. Signed-off-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
#include "vty.h"
lib, zebra: The Bulk of the conversion over to NS and VRF Convert the rest of zebra over to use a Namespae and VRF. Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com> Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2016-02-01 19:55:42 +01:00
#include "vrf.h"
Initial revision
2002-12-13 21:15:29 +01:00
zebra: clean up zapi organization zserv.c has become something of a dumping ground for everything vaguely related to ZAPI and really needs some love. This change splits out the code fo building and consuming ZAPI messages into a separate source file, leaving the actual session and client lifecycle code in zserv.c. Unfortunately since the #include situation in Zebra has not been paid much attention I was forced to fix the headers in a lot of other source files. This is a net improvement overall though. Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
2018-04-22 22:01:20 +02:00
#include "zebra/zserv.h"
#include "zebra/rib.h"
add cplusplus guards to all zebra headers Signed-off-by: Emanuele Di Pascale <emanuele@voltanet.io>
2019-03-25 15:11:55 +01:00
#ifdef __cplusplus
extern "C" {
#endif
zebra: reorganize zserv, batch i/o Group send and receive functions together, change handlers to take a message instead of looking at ->ibuf and ->obuf, allow zebra to read multiple packets off the wire at a time. Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
2018-03-07 00:08:37 +01:00
/* ZAPI command handlers */
zebra: standardize ZAPI message handler args A lot of the handler functions that are called directly from the ZAPI input processing code take different argument sets where they don't need to. These functions are called from only one place and all have the same fundamental information available to them to do their work. There is no need to specialize what information is passed to them; it is cleaner and easier to understand when they all accept the same base set of information and extract what they need inline. Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
2018-03-06 23:57:33 +01:00
extern void zebra_redistribute_add(ZAPI_HANDLER_ARGS);
extern void zebra_redistribute_delete(ZAPI_HANDLER_ARGS);
extern void zebra_redistribute_default_add(ZAPI_HANDLER_ARGS);
extern void zebra_redistribute_default_delete(ZAPI_HANDLER_ARGS);
zebra: reorganize zserv, batch i/o Group send and receive functions together, change handlers to take a message instead of looking at ->ibuf and ->obuf, allow zebra to read multiple packets off the wire at a time. Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
2018-03-07 00:08:37 +01:00
/* ----------------- */
Initial revision
2002-12-13 21:15:29 +01:00
zebra: Convert redistribute_update to use a route_node FRR is passing around a bunch of data that is encapsulated within the route node. Let's just pass that around instead. Signed-off-by: Donald Sharp <sharpd@nvidia.com> Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-01-14 16:00:01 +01:00
extern void redistribute_update(const struct route_node *rn,
zebra: revise redistribution delete to improve update case When selecting a new best route, zebra sends a redist update when the route is installed. There are cases where redist clients may not see that redist add - clients who are not subscribed to the new route type, e.g. In that case, attempt to send a redist delete for the old/previous route type. Revised the redist delete api to accomodate both cases; also tightened up the const-ness of a few internal redist apis. Signed-off-by: Mark Stapp <mjs@voltanet.io>
2019-08-14 19:30:24 +02:00
const struct route_entry *re,
const struct route_entry *prev_re);
/*
* During a route delete, where 'new_re' is NULL, redist a delete to all
* clients registered for the type of 'old_re'.
* During a route update, redist a delete to any clients who will not see
* an update when the new route is installed. There are cases when a client
* may have seen a redist for 'old_re', but will not see
* the redist for 'new_re'.
*/
zebra: Convert redistribute_delete to use a route_node FRR is passing around a bunch of data that is encapsulated within the route node. Let's just pass that around instead. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-01-14 15:48:00 +01:00
void redistribute_delete(const struct route_node *rn,
zebra: revise redistribution delete to improve update case When selecting a new best route, zebra sends a redist update when the route is installed. There are cases where redist clients may not see that redist add - clients who are not subscribed to the new route type, e.g. In that case, attempt to send a redist delete for the old/previous route type. Revised the redist delete api to accomodate both cases; also tightened up the const-ness of a few internal redist apis. Signed-off-by: Mark Stapp <mjs@voltanet.io>
2019-08-14 19:30:24 +02:00
const struct route_entry *old_re,
const struct route_entry *new_re);
Initial revision
2002-12-13 21:15:29 +01:00
zebra: Fix redistribute.h up to our standards FRR must give variable names instead of not defining them in the .h file. This just cleans up this problem for redistribute.h Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-01-14 17:30:31 +01:00
extern void zebra_interface_up_update(struct interface *ifp);
extern void zebra_interface_down_update(struct interface *ifp);
Initial revision
2002-12-13 21:15:29 +01:00
zebra: Fix redistribute.h up to our standards FRR must give variable names instead of not defining them in the .h file. This just cleans up this problem for redistribute.h Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-01-14 17:30:31 +01:00
extern void zebra_interface_add_update(struct interface *ifp);
extern void zebra_interface_delete_update(struct interface *ifp);
Initial revision
2002-12-13 21:15:29 +01:00
zebra: Fix redistribute.h up to our standards FRR must give variable names instead of not defining them in the .h file. This just cleans up this problem for redistribute.h Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-01-14 17:30:31 +01:00
extern void zebra_interface_address_add_update(struct interface *ifp,
struct connected *c);
extern void zebra_interface_address_delete_update(struct interface *ifp,
2005-06-28 Paul Jakma <paul.jakma@sun.com> * (global) Extern and static'ification, with related fixups of declarations, ensuring files include their own headers, etc. if_ioctl.c: (interface_info_ioctl) fix obvious arg mis-order in list loop
2005-06-28 19:17:12 +02:00
struct connected *c);
zebra: Fix redistribute.h up to our standards FRR must give variable names instead of not defining them in the .h file. This just cleans up this problem for redistribute.h Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-01-14 17:30:31 +01:00
extern void zebra_interface_parameters_update(struct interface *ifp);
extern void zebra_interface_vrf_update_del(struct interface *ifp,
Quagga: Implement VRF change semantics for an interface Implement VRF change semantics for an interface to be invoked when an interface is moved from one VRF (e.g., the Default) to another. This includes the message definition as well as updating, deleting or adding the interface from clients, depending on their interest in the VRFs (old and new). Also handle replay of the addresses on the interface upon VRF change, if required. Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com> Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com> Reviewed-by: Don Slice <dslice@cumulusnetworks.com> Ticket: CM-9527 Reviewed By: CCR-4174 Testing Done: Manual tests of various scenarios
2016-02-25 20:30:53 +01:00
vrf_id_t new_vrf_id);
zebra: Fix redistribute.h up to our standards FRR must give variable names instead of not defining them in the .h file. This just cleans up this problem for redistribute.h Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2022-01-14 17:30:31 +01:00
extern void zebra_interface_vrf_update_add(struct interface *ifp,
Quagga: Implement VRF change semantics for an interface Implement VRF change semantics for an interface to be invoked when an interface is moved from one VRF (e.g., the Default) to another. This includes the message definition as well as updating, deleting or adding the interface from clients, depending on their interest in the VRFs (old and new). Also handle replay of the addresses on the interface upon VRF change, if required. Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com> Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com> Reviewed-by: Don Slice <dslice@cumulusnetworks.com> Ticket: CM-9527 Reviewed By: CCR-4174 Testing Done: Manual tests of various scenarios
2016-02-25 20:30:53 +01:00
vrf_id_t old_vrf_id);
zebra: Add route-map support to ip import-table Added the ability to supply a route-map to the ip import-table command, which greatly improves filtering between the kernel prefixes in a non-default table that are imported into the zebra rib. Ticket:CM-8168 Signed-off-by: Donald Slice Reviewed By: Donald Sharp
2016-05-11 17:47:02 +02:00
zebra: Add ability to import alternate tables into the MRIB Expanded the cli command to include an mrib flag for importing to the main table MRIB instead of the main table URIB. Piped through specifying the safi through the import table functions rather than hardcoding to SAFI_UNICAST. Import still only import routes from the URIB subtable, only added the ability to import into the main table MRIB. Signed-off-by: Nathan Bahr <nbahr@atcorp.com>
2024-10-28 19:55:49 +01:00
extern int zebra_import_table(afi_t afi, safi_t safi, vrf_id_t vrf_id, uint32_t table_id,
uint32_t distance, const char *rmap_name, bool add);
zebra-redistribute-table.patch Zebra: Redistribute routes from non-main kernel table to main. This can be the basis for many interesting features such as variations of redistribute ARP, using zebra as the RIB in the presence of multiple routing protocol stacks etc. The code only supports IPv4 for now, but the infrastructure is in place for IPv6. Usage: There is a new route type introduced by this model: TABLE. Routes imported from alternate kernel tables will have their protocol type set to TABLE. Routes from alternate kernel tables MUST be first imported into the main table via "ip import-table <table id>". They can then be redistributed via a routing protocol via the "redistribute table" command. Each imported table can an optional administrative distance specified. In Zebra, a route with a lower distance is chosen over routes with a higher distance. So, distance is how the user can choose to prioritize routes from a particular table over routes from other tables or routes learnt another way in zebra. Route maps for imported tables are specified via "ip protocol" command in zebra. Route maps for redistributed routes within a routing protocol are subject to the route map options supported by the protocol. The "match source-protocol" option in route maps can match against "table" to filter routes learnt from alternate kernel routing tables. Signed-off-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
zebra: Add ability to import alternate tables into the MRIB Expanded the cli command to include an mrib flag for importing to the main table MRIB instead of the main table URIB. Piped through specifying the safi through the import table functions rather than hardcoding to SAFI_UNICAST. Import still only import routes from the URIB subtable, only added the ability to import into the main table MRIB. Signed-off-by: Nathan Bahr <nbahr@atcorp.com>
2024-10-28 19:55:49 +01:00
extern int zebra_add_import_table_entry(struct zebra_vrf *zvrf, safi_t safi, struct route_node *rn,
struct route_entry *re, const char *rmap_name);
extern int zebra_del_import_table_entry(struct zebra_vrf *zvrf, safi_t safi, struct route_node *rn,
zebra: Refactor 'struct rib' to be 'struct route_entry' The 'struct rib' data structure is missnamed. It really is a 'struct route_entry' as part of the 'struct route_node'. We have 1 'struct route_entry' per route src. As such 1 route node can have multiple route entries if multiple protocols attempt to install the same route. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2017-06-01 13:26:25 +02:00
struct route_entry *re);
zebra: Add ability to import alternate tables into the MRIB Expanded the cli command to include an mrib flag for importing to the main table MRIB instead of the main table URIB. Piped through specifying the safi through the import table functions rather than hardcoding to SAFI_UNICAST. Import still only import routes from the URIB subtable, only added the ability to import into the main table MRIB. Signed-off-by: Nathan Bahr <nbahr@atcorp.com>
2024-10-28 19:55:49 +01:00
extern int is_zebra_import_table_enabled(afi_t, safi_t safi, vrf_id_t vrf_id, uint32_t table_id);
zebra-redistribute-table.patch Zebra: Redistribute routes from non-main kernel table to main. This can be the basis for many interesting features such as variations of redistribute ARP, using zebra as the RIB in the presence of multiple routing protocol stacks etc. The code only supports IPv4 for now, but the infrastructure is in place for IPv6. Usage: There is a new route type introduced by this model: TABLE. Routes imported from alternate kernel tables will have their protocol type set to TABLE. Routes from alternate kernel tables MUST be first imported into the main table via "ip import-table <table id>". They can then be redistributed via a routing protocol via the "redistribute table" command. Each imported table can an optional administrative distance specified. In Zebra, a route with a lower distance is chosen over routes with a higher distance. So, distance is how the user can choose to prioritize routes from a particular table over routes from other tables or routes learnt another way in zebra. Route maps for imported tables are specified via "ip protocol" command in zebra. Route maps for redistributed routes within a routing protocol are subject to the route map options supported by the protocol. The "match source-protocol" option in route maps can match against "table" to filter routes learnt from alternate kernel routing tables. Signed-off-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
zebra: Push VRF_DEFAULT outside of import table code The import table code assumes that they will only work in the default vrf. This is ok, but we should push the vrf_id and zvrf to be passed in instead of just using VRF_DEFAULT. This will allow us to fix a couple of things: 1) A bug in import where we are not creating the route entry with the appropriate table so the imported entry is showing up in the wrong spot. 2) In the future allow `ip import-table X` to become vrf aware very easily. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2019-06-25 23:07:30 +02:00
extern int zebra_import_table_config(struct vty *, vrf_id_t vrf_id);
zebra-redistribute-table.patch Zebra: Redistribute routes from non-main kernel table to main. This can be the basis for many interesting features such as variations of redistribute ARP, using zebra as the RIB in the presence of multiple routing protocol stacks etc. The code only supports IPv4 for now, but the infrastructure is in place for IPv6. Usage: There is a new route type introduced by this model: TABLE. Routes imported from alternate kernel tables will have their protocol type set to TABLE. Routes from alternate kernel tables MUST be first imported into the main table via "ip import-table <table id>". They can then be redistributed via a routing protocol via the "redistribute table" command. Each imported table can an optional administrative distance specified. In Zebra, a route with a lower distance is chosen over routes with a higher distance. So, distance is how the user can choose to prioritize routes from a particular table over routes from other tables or routes learnt another way in zebra. Route maps for imported tables are specified via "ip protocol" command in zebra. Route maps for redistributed routes within a routing protocol are subject to the route map options supported by the protocol. The "match source-protocol" option in route maps can match against "table" to filter routes learnt from alternate kernel routing tables. Signed-off-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
zebra : Zebra does not properly track which route-maps are changed (#2493) * Check for the modified routemap in zebra_route_map_process_update_cb() * Added zebra_rib_table_rm_update() for RIB routemap processing * Added zebra_nht_rm_update() for NHT routemap processing Signed-off-by: kssoman <somanks@vmware.com>
2018-08-17 17:47:48 +02:00
extern void zebra_import_table_rm_update(const char *rmap);
add cplusplus guards to all zebra headers Signed-off-by: Emanuele Di Pascale <emanuele@voltanet.io>
2019-03-25 15:11:55 +01:00
#ifdef __cplusplus
}
#endif
Initial revision
2002-12-13 21:15:29 +01:00
#endif /* _ZEBRA_REDISTRIBUTE_H */
Copy permalink