2002-12-13 21:15:29 +01:00
|
|
|
/* zebra client
|
2017-05-13 10:25:29 +02:00
|
|
|
* Copyright (C) 1997, 98, 99 Kunihiro Ishiguro
|
|
|
|
*
|
|
|
|
* This file is part of GNU Zebra.
|
|
|
|
*
|
|
|
|
* GNU Zebra is free software; you can redistribute it and/or modify it
|
|
|
|
* under the terms of the GNU General Public License as published by the
|
|
|
|
* Free Software Foundation; either version 2, or (at your option) any
|
|
|
|
* later version.
|
|
|
|
*
|
|
|
|
* GNU Zebra is distributed in the hope that it will be useful, but
|
|
|
|
* WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License along
|
|
|
|
* with this program; see the file COPYING; if not, write to the Free Software
|
|
|
|
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
|
|
|
|
*/
|
2002-12-13 21:15:29 +01:00
|
|
|
|
|
|
|
#include <zebra.h>
|
|
|
|
|
|
|
|
#include "command.h"
|
|
|
|
#include "stream.h"
|
|
|
|
#include "network.h"
|
|
|
|
#include "prefix.h"
|
|
|
|
#include "log.h"
|
|
|
|
#include "sockunion.h"
|
|
|
|
#include "zclient.h"
|
|
|
|
#include "routemap.h"
|
|
|
|
#include "thread.h"
|
2015-05-20 03:03:47 +02:00
|
|
|
#include "queue.h"
|
2015-08-26 16:44:57 +02:00
|
|
|
#include "memory.h"
|
2015-08-12 15:59:18 +02:00
|
|
|
#include "lib/json.h"
|
2016-06-21 12:39:58 +02:00
|
|
|
#include "lib/bfd.h"
|
2016-01-07 16:03:01 +01:00
|
|
|
#include "filter.h"
|
2017-03-09 15:54:20 +01:00
|
|
|
#include "mpls.h"
|
2017-05-15 23:34:04 +02:00
|
|
|
#include "vxlan.h"
|
2002-12-13 21:15:29 +01:00
|
|
|
|
|
|
|
#include "bgpd/bgpd.h"
|
|
|
|
#include "bgpd/bgp_route.h"
|
|
|
|
#include "bgpd/bgp_attr.h"
|
|
|
|
#include "bgpd/bgp_nexthop.h"
|
|
|
|
#include "bgpd/bgp_zebra.h"
|
|
|
|
#include "bgpd/bgp_fsm.h"
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
#include "bgpd/bgp_debug.h"
|
2011-07-21 05:47:07 +02:00
|
|
|
#include "bgpd/bgp_mpath.h"
|
2015-05-20 02:40:34 +02:00
|
|
|
#include "bgpd/bgp_nexthop.h"
|
2015-05-20 03:12:17 +02:00
|
|
|
#include "bgpd/bgp_nht.h"
|
2016-09-08 19:03:30 +02:00
|
|
|
#include "bgpd/bgp_bfd.h"
|
2017-03-09 15:54:20 +01:00
|
|
|
#include "bgpd/bgp_label.h"
|
bgpd: add L3/L2VPN Virtual Network Control feature
This feature adds an L3 & L2 VPN application that makes use of the VPN
and Encap SAFIs. This code is currently used to support IETF NVO3 style
operation. In NVO3 terminology it provides the Network Virtualization
Authority (NVA) and the ability to import/export IP prefixes and MAC
addresses from Network Virtualization Edges (NVEs). The code supports
per-NVE tables.
The NVE-NVA protocol used to communicate routing and Ethernet / Layer 2
(L2) forwarding information between NVAs and NVEs is referred to as the
Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. For
general background on NVO3 and RFP concepts see [1]. For information on
Openflow see [2].
RFPs are integrated with BGP via the RF API contained in the new "rfapi"
BGP sub-directory. Currently, only a simple example RFP is included in
Quagga. Developers may use this example as a starting point to integrate
Quagga with an RFP of their choosing, e.g., OpenFlow. The RFAPI code
also supports the ability import/export of routing information between
VNC and customer edge routers (CEs) operating within a virtual
network. Import/export may take place between BGP views or to the
default zebera VRF.
BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VPN
information between NVAs. BGP based IP VPN support is defined in
RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659,
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Use
of both the Encapsulation Subsequent Address Family Identifier (SAFI)
and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute, are supported. MAC address distribution does
not follow any standard BGB encoding, although it was inspired by the
early IETF EVPN concepts.
The feature is conditionally compiled and disabled by default.
Use the --enable-bgp-vnc configure option to enable.
The majority of this code was authored by G. Paul Ziemba
<paulz@labn.net>.
[1] http://tools.ietf.org/html/draft-ietf-nvo3-nve-nva-cp-req
[2] https://www.opennetworking.org/sdn-resources/technical-library
Now includes changes needed to merge with cmaster-next.
2016-05-07 20:18:56 +02:00
|
|
|
#if ENABLE_BGP_VNC
|
2017-07-17 14:03:14 +02:00
|
|
|
#include "bgpd/rfapi/rfapi_backend.h"
|
|
|
|
#include "bgpd/rfapi/vnc_export_bgp.h"
|
bgpd: add L3/L2VPN Virtual Network Control feature
This feature adds an L3 & L2 VPN application that makes use of the VPN
and Encap SAFIs. This code is currently used to support IETF NVO3 style
operation. In NVO3 terminology it provides the Network Virtualization
Authority (NVA) and the ability to import/export IP prefixes and MAC
addresses from Network Virtualization Edges (NVEs). The code supports
per-NVE tables.
The NVE-NVA protocol used to communicate routing and Ethernet / Layer 2
(L2) forwarding information between NVAs and NVEs is referred to as the
Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. For
general background on NVO3 and RFP concepts see [1]. For information on
Openflow see [2].
RFPs are integrated with BGP via the RF API contained in the new "rfapi"
BGP sub-directory. Currently, only a simple example RFP is included in
Quagga. Developers may use this example as a starting point to integrate
Quagga with an RFP of their choosing, e.g., OpenFlow. The RFAPI code
also supports the ability import/export of routing information between
VNC and customer edge routers (CEs) operating within a virtual
network. Import/export may take place between BGP views or to the
default zebera VRF.
BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VPN
information between NVAs. BGP based IP VPN support is defined in
RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659,
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Use
of both the Encapsulation Subsequent Address Family Identifier (SAFI)
and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute, are supported. MAC address distribution does
not follow any standard BGB encoding, although it was inspired by the
early IETF EVPN concepts.
The feature is conditionally compiled and disabled by default.
Use the --enable-bgp-vnc configure option to enable.
The majority of this code was authored by G. Paul Ziemba
<paulz@labn.net>.
[1] http://tools.ietf.org/html/draft-ietf-nvo3-nve-nva-cp-req
[2] https://www.opennetworking.org/sdn-resources/technical-library
Now includes changes needed to merge with cmaster-next.
2016-05-07 20:18:56 +02:00
|
|
|
#endif
|
2017-05-15 23:34:04 +02:00
|
|
|
#include "bgpd/bgp_evpn.h"
|
2018-03-09 21:52:55 +01:00
|
|
|
#include "bgpd/bgp_mplsvpn.h"
|
2018-04-07 20:13:07 +02:00
|
|
|
#include "bgpd/bgp_labelpool.h"
|
2018-03-08 15:39:19 +01:00
|
|
|
#include "bgpd/bgp_pbr.h"
|
2014-06-04 06:53:35 +02:00
|
|
|
|
2002-12-13 21:15:29 +01:00
|
|
|
/* All information about zebra. */
|
[bgpd] Stability fixes including bugs 397, 492
I've spent the last several weeks working on stability fixes to bgpd.
These patches fix all of the numerous crashes, assertion failures, memory
leaks and memory stomping I could find. Valgrind was used extensively.
Added new function bgp_exit() to help catch problems. If "debug bgp" is
configured and bgpd exits with status of 0, statistics on remaining
lib/memory.c allocations are printed to stderr. It is my hope that other
developers will use this to stay on top of memory issues.
Example questionable exit:
bgpd: memstats: Current memory utilization in module LIB:
bgpd: memstats: Link List : 6
bgpd: memstats: Link Node : 5
bgpd: memstats: Hash : 8
bgpd: memstats: Hash Bucket : 2
bgpd: memstats: Hash Index : 8
bgpd: memstats: Work queue : 3
bgpd: memstats: Work queue item : 2
bgpd: memstats: Work queue name string : 3
bgpd: memstats: Current memory utilization in module BGP:
bgpd: memstats: BGP instance : 1
bgpd: memstats: BGP peer : 1
bgpd: memstats: BGP peer hostname : 1
bgpd: memstats: BGP attribute : 1
bgpd: memstats: BGP extra attributes : 1
bgpd: memstats: BGP aspath : 1
bgpd: memstats: BGP aspath str : 1
bgpd: memstats: BGP table : 24
bgpd: memstats: BGP node : 1
bgpd: memstats: BGP route : 1
bgpd: memstats: BGP synchronise : 8
bgpd: memstats: BGP Process queue : 1
bgpd: memstats: BGP node clear queue : 1
bgpd: memstats: NOTE: If configuration exists, utilization may be expected.
Example clean exit:
bgpd: memstats: No remaining tracked memory utilization.
This patch fixes bug #397: "Invalid free in bgp_announce_check()".
This patch fixes bug #492: "SIGBUS in bgpd/bgp_route.c:
bgp_clear_route_node()".
My apologies for not separating out these changes into individual patches.
The complexity of doing so boggled what is left of my brain. I hope this
is all still useful to the community.
This code has been production tested, in non-route-server-client mode, on
a linux 32-bit box and a 64-bit box.
Release/reset functions, used by bgp_exit(), added to:
bgpd/bgp_attr.c,h
bgpd/bgp_community.c,h
bgpd/bgp_dump.c,h
bgpd/bgp_ecommunity.c,h
bgpd/bgp_filter.c,h
bgpd/bgp_nexthop.c,h
bgpd/bgp_route.c,h
lib/routemap.c,h
File by file analysis:
* bgpd/bgp_aspath.c: Prevent re-use of ashash after it is released.
* bgpd/bgp_attr.c: #if removed uncalled cluster_dup().
* bgpd/bgp_clist.c,h: Allow community_list_terminate() to be called from
bgp_exit().
* bgpd/bgp_filter.c: Fix aslist->name use without allocation check, and
also fix memory leak.
* bgpd/bgp_main.c: Created bgp_exit() exit routine. This function frees
allocations made as part of bgpd initialization and, to some extent,
configuration. If "debug bgp" is configured, memory stats are printed
as described above.
* bgpd/bgp_nexthop.c: zclient_new() already allocates stream for
ibuf/obuf, so bgp_scan_init() shouldn't do it too. Also, made it so
zlookup is global so bgp_exit() can use it.
* bgpd/bgp_packet.c: bgp_capability_msg_parse() call to bgp_clear_route()
adjusted to use new BGP_CLEAR_ROUTE_NORMAL flag.
* bgpd/bgp_route.h: Correct reference counter "lock" to be signed.
bgp_clear_route() now accepts a bgp_clear_route_type of either
BGP_CLEAR_ROUTE_NORMAL or BGP_CLEAR_ROUTE_MY_RSCLIENT.
* bgpd/bgp_route.c:
- bgp_process_rsclient(): attr was being zero'ed and then
bgp_attr_extra_free() was being called with it, even though it was
never filled with valid data.
- bgp_process_rsclient(): Make sure rsclient->group is not NULL before
use.
- bgp_processq_del(): Add call to bgp_table_unlock().
- bgp_process(): Add call to bgp_table_lock().
- bgp_update_rsclient(): memset clearing of new_attr not needed since
declarationw with "= { 0 }" does it. memset was already commented
out.
- bgp_update_rsclient(): Fix screwed up misleading indentation.
- bgp_withdraw_rsclient(): Fix screwed up misleading indentation.
- bgp_clear_route_node(): Support BGP_CLEAR_ROUTE_MY_RSCLIENT.
- bgp_clear_node_queue_del(): Add call to bgp_table_unlock() and also
free struct bgp_clear_node_queue used for work item.
- bgp_clear_node_complete(): Do peer_unlock() after BGP_EVENT_ADD() in
case peer is released by peer_unlock() call.
- bgp_clear_route_table(): Support BGP_CLEAR_ROUTE_MY_RSCLIENT. Use
struct bgp_clear_node_queue to supply data to worker. Add call to
bgp_table_lock().
- bgp_clear_route(): Add support for BGP_CLEAR_ROUTE_NORMAL or
BGP_CLEAR_ROUTE_MY_RSCLIENT.
- bgp_clear_route_all(): Use BGP_CLEAR_ROUTE_NORMAL.
Bug 397 fixes:
- bgp_default_originate()
- bgp_announce_table()
* bgpd/bgp_table.h:
- struct bgp_table: Added reference count. Changed type of owner to be
"struct peer *" rather than "void *".
- struct bgp_node: Correct reference counter "lock" to be signed.
* bgpd/bgp_table.c:
- Added bgp_table reference counting.
- bgp_table_free(): Fixed cleanup code. Call peer_unlock() on owner if
set.
- bgp_unlock_node(): Added assertion.
- bgp_node_get(): Added call to bgp_lock_node() to code path that it was
missing from.
* bgpd/bgp_vty.c:
- peer_rsclient_set_vty(): Call peer_lock() as part of peer assignment
to owner. Handle failure gracefully.
- peer_rsclient_unset_vty(): Add call to bgp_clear_route() with
BGP_CLEAR_ROUTE_MY_RSCLIENT purpose.
* bgpd/bgp_zebra.c: Made it so zclient is global so bgp_exit() can use it.
* bgpd/bgpd.c:
- peer_lock(): Allow to be called when status is "Deleted".
- peer_deactivate(): Supply BGP_CLEAR_ROUTE_NORMAL purpose to
bgp_clear_route() call.
- peer_delete(): Common variable listnode pn. Fix bug in which rsclient
was only dealt with if not part of a peer group. Call
bgp_clear_route() for rsclient, if appropriate, and do so with
BGP_CLEAR_ROUTE_MY_RSCLIENT purpose.
- peer_group_get(): Use XSTRDUP() instead of strdup() for conf->host.
- peer_group_bind(): Call bgp_clear_route() for rsclient, and do so with
BGP_CLEAR_ROUTE_MY_RSCLIENT purpose.
- bgp_create(): Use XSTRDUP() instead of strdup() for peer_self->host.
- bgp_delete(): Delete peers before groups, rather than after. And then
rather than deleting rsclients, verify that there are none at this
point.
- bgp_unlock(): Add assertion.
- bgp_free(): Call bgp_table_finish() rather than doing XFREE() itself.
* lib/command.c,h: Compiler warning fixes. Add cmd_terminate(). Fixed
massive leak in install_element() in which cmd_make_descvec() was being
called more than once for the same cmd->strvec/string/doc.
* lib/log.c: Make closezlog() check fp before calling fclose().
* lib/memory.c: Catch when alloc count goes negative by using signed
counts. Correct #endif comment. Add log_memstats_stderr().
* lib/memory.h: Add log_memstats_stderr().
* lib/thread.c: thread->funcname was being accessed in thread_call() after
it had been freed. Rearranged things so that thread_call() frees
funcname. Also made it so thread_master_free() cleans up cpu_record.
* lib/vty.c,h: Use global command_cr. Add vty_terminate().
* lib/zclient.c,h: Re-enable zclient_free().
2009-07-18 07:44:03 +02:00
|
|
|
struct zclient *zclient = NULL;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2016-02-12 21:18:28 +01:00
|
|
|
/* Can we install into zebra? */
|
2017-07-17 14:03:14 +02:00
|
|
|
static inline int bgp_install_info_to_zebra(struct bgp *bgp)
|
2016-02-12 21:18:28 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
if (zclient->sock <= 0)
|
|
|
|
return 0;
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (!IS_BGP_INST_KNOWN_TO_ZEBRA(bgp))
|
|
|
|
return 0;
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return 1;
|
2016-02-12 21:18:28 +01:00
|
|
|
}
|
|
|
|
|
2016-10-07 15:44:42 +02:00
|
|
|
int zclient_num_connects;
|
|
|
|
|
2004-10-03 20:18:34 +02:00
|
|
|
/* Router-id update message from zebra. */
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_router_id_update(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct prefix router_id;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
zebra_router_id_update_read(zclient->ibuf, &router_id);
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA)) {
|
|
|
|
char buf[PREFIX2STR_BUFFER];
|
|
|
|
prefix2str(&router_id, buf, sizeof(buf));
|
|
|
|
zlog_debug("Rx Router Id update VRF %u Id %s", vrf_id, buf);
|
|
|
|
}
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_router_id_zebra_bump(vrf_id, &router_id);
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2015-05-20 02:40:34 +02:00
|
|
|
/* Nexthop update message from zebra. */
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_read_nexthop_update(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2015-05-20 02:40:34 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_parse_nexthop_update(command, vrf_id);
|
|
|
|
return 0;
|
2015-05-20 03:04:20 +02:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_read_import_check_update(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2015-05-20 03:04:20 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_parse_nexthop_update(command, vrf_id);
|
|
|
|
return 0;
|
2015-05-20 02:40:34 +02:00
|
|
|
}
|
|
|
|
|
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
|
|
|
/* Set or clear interface on which unnumbered neighbor is configured. This
|
|
|
|
* would in turn cause BGP to initiate or turn off IPv6 RAs on this
|
|
|
|
* interface.
|
|
|
|
*/
|
2017-07-17 14:03:14 +02:00
|
|
|
static void bgp_update_interface_nbrs(struct bgp *bgp, struct interface *ifp,
|
|
|
|
struct interface *upd_ifp)
|
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
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *node, *nnode;
|
|
|
|
struct peer *peer;
|
|
|
|
|
|
|
|
for (ALL_LIST_ELEMENTS(bgp->peer, node, nnode, peer)) {
|
|
|
|
if (peer->conf_if && (strcmp(peer->conf_if, ifp->name) == 0)) {
|
|
|
|
if (upd_ifp) {
|
|
|
|
peer->ifp = upd_ifp;
|
|
|
|
bgp_zebra_initiate_radv(bgp, peer);
|
|
|
|
} else {
|
|
|
|
bgp_zebra_terminate_radv(bgp, peer);
|
|
|
|
peer->ifp = upd_ifp;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
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
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_read_fec_update(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length)
|
2017-03-09 15:54:20 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_parse_fec_update();
|
|
|
|
return 0;
|
2017-03-09 15:54:20 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static void bgp_start_interface_nbrs(struct bgp *bgp, struct interface *ifp)
|
2015-05-20 02:40:40 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *node, *nnode;
|
|
|
|
struct peer *peer;
|
|
|
|
|
|
|
|
for (ALL_LIST_ELEMENTS(bgp->peer, node, nnode, peer)) {
|
|
|
|
if (peer->conf_if && (strcmp(peer->conf_if, ifp->name) == 0)
|
|
|
|
&& peer->status != Established) {
|
|
|
|
if (peer_active(peer))
|
|
|
|
BGP_EVENT_ADD(peer, BGP_Stop);
|
|
|
|
BGP_EVENT_ADD(peer, BGP_Start);
|
|
|
|
}
|
|
|
|
}
|
2015-05-20 02:40:40 +02:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static void bgp_nbr_connected_add(struct bgp *bgp, struct nbr_connected *ifc)
|
2015-06-12 16:59:09 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *node;
|
|
|
|
struct connected *connected;
|
|
|
|
struct interface *ifp;
|
|
|
|
struct prefix *p;
|
|
|
|
|
|
|
|
/* Kick-off the FSM for any relevant peers only if there is a
|
|
|
|
* valid local address on the interface.
|
|
|
|
*/
|
|
|
|
ifp = ifc->ifp;
|
|
|
|
for (ALL_LIST_ELEMENTS_RO(ifp->connected, node, connected)) {
|
|
|
|
p = connected->address;
|
|
|
|
if (p->family == AF_INET6
|
|
|
|
&& IN6_IS_ADDR_LINKLOCAL(&p->u.prefix6))
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
if (!connected)
|
|
|
|
return;
|
|
|
|
|
|
|
|
bgp_start_interface_nbrs(bgp, ifp);
|
2015-06-12 16:59:09 +02:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static void bgp_nbr_connected_delete(struct bgp *bgp, struct nbr_connected *ifc,
|
|
|
|
int del)
|
2015-05-20 02:40:40 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *node, *nnode;
|
|
|
|
struct peer *peer;
|
|
|
|
struct interface *ifp;
|
|
|
|
|
|
|
|
for (ALL_LIST_ELEMENTS(bgp->peer, node, nnode, peer)) {
|
|
|
|
if (peer->conf_if
|
|
|
|
&& (strcmp(peer->conf_if, ifc->ifp->name) == 0)) {
|
|
|
|
peer->last_reset = PEER_DOWN_NBR_ADDR_DEL;
|
|
|
|
BGP_EVENT_ADD(peer, BGP_Stop);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* Free neighbor also, if we're asked to. */
|
|
|
|
if (del) {
|
|
|
|
ifp = ifc->ifp;
|
|
|
|
listnode_delete(ifp->nbr_connected, ifc);
|
|
|
|
nbr_connected_free(ifc);
|
|
|
|
}
|
2015-05-20 02:40:40 +02:00
|
|
|
}
|
|
|
|
|
2002-12-13 21:15:29 +01:00
|
|
|
/* Inteface addition message from zebra. */
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_add(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct interface *ifp;
|
|
|
|
struct bgp *bgp;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
ifp = zebra_interface_add_read(zclient->ibuf, vrf_id);
|
|
|
|
if (!ifp) // unexpected
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA) && ifp)
|
|
|
|
zlog_debug("Rx Intf add VRF %u IF %s", vrf_id, ifp->name);
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
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
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_update_interface_nbrs(bgp, ifp, ifp);
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_delete(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct stream *s;
|
|
|
|
struct interface *ifp;
|
|
|
|
struct bgp *bgp;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-10-09 17:22:52 +02:00
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
s = zclient->ibuf;
|
|
|
|
ifp = zebra_interface_state_read(s, vrf_id);
|
|
|
|
if (!ifp) /* This may happen if we've just unregistered for a VRF. */
|
|
|
|
return 0;
|
2016-03-02 08:40:14 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Rx Intf del VRF %u IF %s", vrf_id, ifp->name);
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_update_interface_nbrs(bgp, ifp, NULL);
|
2017-07-26 15:57:35 +02:00
|
|
|
|
2017-10-03 03:06:04 +02:00
|
|
|
if_set_index(ifp, IFINDEX_INTERNAL);
|
2017-07-17 14:03:14 +02:00
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_up(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct stream *s;
|
|
|
|
struct interface *ifp;
|
|
|
|
struct connected *c;
|
|
|
|
struct nbr_connected *nc;
|
|
|
|
struct listnode *node, *nnode;
|
|
|
|
struct bgp *bgp;
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-10-09 17:22:52 +02:00
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
s = zclient->ibuf;
|
|
|
|
ifp = zebra_interface_state_read(s, vrf_id);
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (!ifp)
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Rx Intf up VRF %u IF %s", vrf_id, ifp->name);
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(ifp->connected, node, nnode, c))
|
|
|
|
bgp_connected_add(bgp, c);
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(ifp->nbr_connected, node, nnode, nc))
|
|
|
|
bgp_nbr_connected_add(bgp, nc);
|
2015-05-20 02:40:40 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_down(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct stream *s;
|
|
|
|
struct interface *ifp;
|
|
|
|
struct connected *c;
|
|
|
|
struct nbr_connected *nc;
|
|
|
|
struct listnode *node, *nnode;
|
|
|
|
struct bgp *bgp;
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-10-09 17:22:52 +02:00
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
s = zclient->ibuf;
|
|
|
|
ifp = zebra_interface_state_read(s, vrf_id);
|
|
|
|
if (!ifp)
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Rx Intf down VRF %u IF %s", vrf_id, ifp->name);
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(ifp->connected, node, nnode, c))
|
|
|
|
bgp_connected_delete(bgp, c);
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(ifp->nbr_connected, node, nnode, nc))
|
|
|
|
bgp_nbr_connected_delete(bgp, nc, 1);
|
2015-05-20 02:40:40 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Fast external-failover */
|
|
|
|
{
|
|
|
|
struct peer *peer;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (CHECK_FLAG(bgp->flags, BGP_FLAG_NO_FAST_EXT_FAILOVER))
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(bgp->peer, node, nnode, peer)) {
|
2016-09-08 19:03:30 +02:00
|
|
|
#if defined(HAVE_CUMULUS)
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Take down directly connected EBGP peers as well as
|
|
|
|
* 1-hop BFD
|
|
|
|
* tracked (directly connected) IBGP peers.
|
|
|
|
*/
|
|
|
|
if ((peer->ttl != 1) && (peer->gtsm_hops != 1)
|
|
|
|
&& (!peer->bfd_info
|
|
|
|
|| bgp_bfd_is_peer_multihop(peer)))
|
2016-09-08 19:03:30 +02:00
|
|
|
#else
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Take down directly connected EBGP peers */
|
|
|
|
if ((peer->ttl != 1) && (peer->gtsm_hops != 1))
|
2016-09-08 19:03:30 +02:00
|
|
|
#endif
|
2017-07-17 14:03:14 +02:00
|
|
|
continue;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (ifp == peer->nexthop.ifp) {
|
|
|
|
BGP_EVENT_ADD(peer, BGP_Stop);
|
|
|
|
peer->last_reset = PEER_DOWN_IF_DOWN;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_address_add(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct connected *ifc;
|
2017-10-09 17:22:52 +02:00
|
|
|
struct bgp *bgp;
|
|
|
|
|
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
|
|
|
ifc = zebra_interface_address_read(command, zclient->ibuf, vrf_id);
|
|
|
|
|
|
|
|
if (ifc == NULL)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (bgp_debug_zebra(ifc->address)) {
|
|
|
|
char buf[PREFIX2STR_BUFFER];
|
|
|
|
prefix2str(ifc->address, buf, sizeof(buf));
|
|
|
|
zlog_debug("Rx Intf address add VRF %u IF %s addr %s", vrf_id,
|
|
|
|
ifc->ifp->name, buf);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (if_is_operative(ifc->ifp)) {
|
|
|
|
bgp_connected_add(bgp, ifc);
|
2017-10-09 17:22:52 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* If we have learnt of any neighbors on this interface,
|
|
|
|
* check to kick off any BGP interface-based neighbors,
|
|
|
|
* but only if this is a link-local address.
|
|
|
|
*/
|
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(&ifc->address->u.prefix6)
|
|
|
|
&& !list_isempty(ifc->ifp->nbr_connected))
|
|
|
|
bgp_start_interface_nbrs(bgp, ifc->ifp);
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_address_delete(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct connected *ifc;
|
|
|
|
struct bgp *bgp;
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-10-09 17:22:52 +02:00
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
ifc = zebra_interface_address_read(command, zclient->ibuf, vrf_id);
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (ifc == NULL)
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (bgp_debug_zebra(ifc->address)) {
|
|
|
|
char buf[PREFIX2STR_BUFFER];
|
|
|
|
prefix2str(ifc->address, buf, sizeof(buf));
|
|
|
|
zlog_debug("Rx Intf address del VRF %u IF %s addr %s", vrf_id,
|
|
|
|
ifc->ifp->name, buf);
|
|
|
|
}
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (if_is_operative(ifc->ifp)) {
|
2017-10-09 17:22:52 +02:00
|
|
|
bgp_connected_delete(bgp, ifc);
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
connected_free(ifc);
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_nbr_address_add(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2015-05-20 02:40:40 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct nbr_connected *ifc = NULL;
|
|
|
|
struct bgp *bgp;
|
|
|
|
|
|
|
|
ifc = zebra_interface_nbr_address_read(command, zclient->ibuf, vrf_id);
|
|
|
|
|
|
|
|
if (ifc == NULL)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (bgp_debug_zebra(ifc->address)) {
|
|
|
|
char buf[PREFIX2STR_BUFFER];
|
|
|
|
prefix2str(ifc->address, buf, sizeof(buf));
|
|
|
|
zlog_debug("Rx Intf neighbor add VRF %u IF %s addr %s", vrf_id,
|
|
|
|
ifc->ifp->name, buf);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (if_is_operative(ifc->ifp)) {
|
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (bgp)
|
|
|
|
bgp_nbr_connected_add(bgp, ifc);
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
2015-05-20 02:40:40 +02:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_nbr_address_delete(int command,
|
|
|
|
struct zclient *zclient,
|
|
|
|
zebra_size_t length,
|
|
|
|
vrf_id_t vrf_id)
|
2015-05-20 02:40:40 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct nbr_connected *ifc = NULL;
|
|
|
|
struct bgp *bgp;
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
ifc = zebra_interface_nbr_address_read(command, zclient->ibuf, vrf_id);
|
2015-05-20 02:40:40 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (ifc == NULL)
|
|
|
|
return 0;
|
2015-05-20 02:40:40 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (bgp_debug_zebra(ifc->address)) {
|
|
|
|
char buf[PREFIX2STR_BUFFER];
|
|
|
|
prefix2str(ifc->address, buf, sizeof(buf));
|
|
|
|
zlog_debug("Rx Intf neighbor del VRF %u IF %s addr %s", vrf_id,
|
|
|
|
ifc->ifp->name, buf);
|
|
|
|
}
|
2015-05-20 02:40:40 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (if_is_operative(ifc->ifp)) {
|
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (bgp)
|
|
|
|
bgp_nbr_connected_delete(bgp, ifc, 0);
|
|
|
|
}
|
2015-05-20 02:40:40 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
nbr_connected_free(ifc);
|
2015-05-20 02:40:40 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return 0;
|
2015-05-20 02:40:40 +02:00
|
|
|
}
|
|
|
|
|
2016-02-25 20:39:25 +01:00
|
|
|
/* VRF update for an interface. */
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_interface_vrf_update(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2016-02-25 20:39:25 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct interface *ifp;
|
|
|
|
vrf_id_t new_vrf_id;
|
|
|
|
struct connected *c;
|
|
|
|
struct nbr_connected *nc;
|
|
|
|
struct listnode *node, *nnode;
|
|
|
|
struct bgp *bgp;
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
ifp = zebra_interface_vrf_update_read(zclient->ibuf, vrf_id,
|
|
|
|
&new_vrf_id);
|
|
|
|
if (!ifp)
|
|
|
|
return 0;
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA) && ifp)
|
|
|
|
zlog_debug("Rx Intf VRF change VRF %u IF %s NewVRF %u", vrf_id,
|
|
|
|
ifp->name, new_vrf_id);
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(ifp->connected, node, nnode, c))
|
|
|
|
bgp_connected_delete(bgp, c);
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(ifp->nbr_connected, node, nnode, nc))
|
|
|
|
bgp_nbr_connected_delete(bgp, nc, 1);
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Fast external-failover */
|
|
|
|
{
|
|
|
|
struct peer *peer;
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (CHECK_FLAG(bgp->flags, BGP_FLAG_NO_FAST_EXT_FAILOVER))
|
|
|
|
return 0;
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(bgp->peer, node, nnode, peer)) {
|
|
|
|
if ((peer->ttl != 1) && (peer->gtsm_hops != 1))
|
|
|
|
continue;
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (ifp == peer->nexthop.ifp)
|
|
|
|
BGP_EVENT_ADD(peer, BGP_Stop);
|
|
|
|
}
|
|
|
|
}
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if_update_to_new_vrf(ifp, new_vrf_id);
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp = bgp_lookup_by_vrf_id(new_vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(ifp->connected, node, nnode, c))
|
|
|
|
bgp_connected_add(bgp, c);
|
2016-02-25 20:39:25 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS(ifp->nbr_connected, node, nnode, nc))
|
|
|
|
bgp_nbr_connected_add(bgp, nc);
|
|
|
|
return 0;
|
2016-02-25 20:39:25 +01:00
|
|
|
}
|
|
|
|
|
2002-12-13 21:15:29 +01:00
|
|
|
/* Zebra route add and delete treatment. */
|
2017-08-21 03:10:50 +02:00
|
|
|
static int zebra_read_route(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-11-15 19:22:56 +01:00
|
|
|
enum nexthop_types_t nhtype;
|
2017-08-21 03:10:50 +02:00
|
|
|
struct zapi_route api;
|
|
|
|
union g_addr nexthop;
|
2017-11-15 19:22:56 +01:00
|
|
|
ifindex_t ifindex;
|
2017-08-21 03:10:50 +02:00
|
|
|
int add, i;
|
2017-07-17 14:03:14 +02:00
|
|
|
struct bgp *bgp;
|
|
|
|
|
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
|
|
|
|
2017-08-21 03:10:50 +02:00
|
|
|
if (zapi_route_decode(zclient->ibuf, &api) < 0)
|
|
|
|
return -1;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 03:10:50 +02:00
|
|
|
/* we completely ignore srcdest routes for now. */
|
|
|
|
if (CHECK_FLAG(api.message, ZAPI_MESSAGE_SRCPFX))
|
|
|
|
return 0;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 03:10:50 +02:00
|
|
|
/* ignore link-local address. */
|
|
|
|
if (api.prefix.family == AF_INET6
|
|
|
|
&& IN6_IS_ADDR_LINKLOCAL(&api.prefix.u.prefix6))
|
|
|
|
return 0;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 03:10:50 +02:00
|
|
|
nexthop = api.nexthops[0].gate;
|
|
|
|
ifindex = api.nexthops[0].ifindex;
|
2017-11-15 19:22:56 +01:00
|
|
|
nhtype = api.nexthops[0].type;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 03:10:50 +02:00
|
|
|
add = (command == ZEBRA_REDISTRIBUTE_ROUTE_ADD);
|
|
|
|
if (add) {
|
2017-07-17 14:03:14 +02:00
|
|
|
/*
|
|
|
|
* The ADD message is actually an UPDATE and there is no
|
|
|
|
* explicit DEL
|
|
|
|
* for a prior redistributed route, if any. So, perform an
|
|
|
|
* implicit
|
|
|
|
* DEL processing for the same redistributed route from any
|
|
|
|
* other
|
|
|
|
* source type.
|
|
|
|
*/
|
|
|
|
for (i = 0; i < ZEBRA_ROUTE_MAX; i++) {
|
|
|
|
if (i != api.type)
|
2017-08-21 03:10:50 +02:00
|
|
|
bgp_redistribute_delete(bgp, &api.prefix, i,
|
2017-07-17 14:03:14 +02:00
|
|
|
api.instance);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Now perform the add/update. */
|
2017-08-21 03:10:50 +02:00
|
|
|
bgp_redistribute_add(bgp, &api.prefix, &nexthop, ifindex,
|
2018-02-09 19:22:50 +01:00
|
|
|
nhtype, api.metric, api.type, api.instance,
|
|
|
|
api.tag);
|
2017-07-17 14:03:14 +02:00
|
|
|
} else {
|
2017-08-21 03:10:50 +02:00
|
|
|
bgp_redistribute_delete(bgp, &api.prefix, api.type,
|
|
|
|
api.instance);
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 03:10:50 +02:00
|
|
|
if (bgp_debug_zebra(&api.prefix)) {
|
|
|
|
char buf[2][PREFIX_STRLEN];
|
|
|
|
|
|
|
|
prefix2str(&api.prefix, buf[0], sizeof(buf[0]));
|
2018-04-05 19:42:27 +02:00
|
|
|
if (add) {
|
|
|
|
inet_ntop(api.prefix.family, &nexthop, buf[1],
|
|
|
|
sizeof(buf[1]));
|
|
|
|
zlog_debug(
|
|
|
|
"Rx route ADD VRF %u %s[%d] %s nexthop %s (type %d if %u) metric %u tag %" ROUTE_TAG_PRI,
|
|
|
|
vrf_id, zebra_route_string(api.type),
|
|
|
|
api.instance, buf[0], buf[1], nhtype,
|
|
|
|
ifindex, api.metric, api.tag);
|
|
|
|
} else {
|
|
|
|
zlog_debug(
|
|
|
|
"Rx route DEL VRF %u %s[%d] %s",
|
|
|
|
vrf_id, zebra_route_string(api.type),
|
|
|
|
api.instance, buf[0]);
|
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2014-06-04 06:53:35 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
struct interface *if_lookup_by_ipv4(struct in_addr *addr, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-10-03 03:06:01 +02:00
|
|
|
struct vrf *vrf;
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *cnode;
|
|
|
|
struct interface *ifp;
|
|
|
|
struct connected *connected;
|
|
|
|
struct prefix_ipv4 p;
|
|
|
|
struct prefix *cp;
|
|
|
|
|
2017-10-03 03:06:01 +02:00
|
|
|
vrf = vrf_lookup_by_id(vrf_id);
|
|
|
|
if (!vrf)
|
|
|
|
return NULL;
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
p.family = AF_INET;
|
|
|
|
p.prefix = *addr;
|
|
|
|
p.prefixlen = IPV4_MAX_BITLEN;
|
|
|
|
|
2017-10-06 20:25:58 +02:00
|
|
|
FOR_ALL_INTERFACES (vrf, ifp) {
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS_RO(ifp->connected, cnode, connected)) {
|
|
|
|
cp = connected->address;
|
|
|
|
|
|
|
|
if (cp->family == AF_INET)
|
|
|
|
if (prefix_match(cp, (struct prefix *)&p))
|
|
|
|
return ifp;
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
return NULL;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
struct interface *if_lookup_by_ipv4_exact(struct in_addr *addr, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-10-03 03:06:01 +02:00
|
|
|
struct vrf *vrf;
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *cnode;
|
|
|
|
struct interface *ifp;
|
|
|
|
struct connected *connected;
|
|
|
|
struct prefix *cp;
|
|
|
|
|
2017-10-03 03:06:01 +02:00
|
|
|
vrf = vrf_lookup_by_id(vrf_id);
|
|
|
|
if (!vrf)
|
|
|
|
return NULL;
|
|
|
|
|
2017-10-06 20:25:58 +02:00
|
|
|
FOR_ALL_INTERFACES (vrf, ifp) {
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS_RO(ifp->connected, cnode, connected)) {
|
|
|
|
cp = connected->address;
|
|
|
|
|
|
|
|
if (cp->family == AF_INET)
|
|
|
|
if (IPV4_ADDR_SAME(&cp->u.prefix4, addr))
|
|
|
|
return ifp;
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
return NULL;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
struct interface *if_lookup_by_ipv6(struct in6_addr *addr, ifindex_t ifindex,
|
|
|
|
vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-10-03 03:06:01 +02:00
|
|
|
struct vrf *vrf;
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *cnode;
|
|
|
|
struct interface *ifp;
|
|
|
|
struct connected *connected;
|
|
|
|
struct prefix_ipv6 p;
|
|
|
|
struct prefix *cp;
|
|
|
|
|
2017-10-03 03:06:01 +02:00
|
|
|
vrf = vrf_lookup_by_id(vrf_id);
|
|
|
|
if (!vrf)
|
|
|
|
return NULL;
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
p.family = AF_INET6;
|
|
|
|
p.prefix = *addr;
|
|
|
|
p.prefixlen = IPV6_MAX_BITLEN;
|
|
|
|
|
2017-10-06 20:25:58 +02:00
|
|
|
FOR_ALL_INTERFACES (vrf, ifp) {
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS_RO(ifp->connected, cnode, connected)) {
|
|
|
|
cp = connected->address;
|
|
|
|
|
|
|
|
if (cp->family == AF_INET6)
|
|
|
|
if (prefix_match(cp, (struct prefix *)&p)) {
|
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(
|
|
|
|
&cp->u.prefix6)) {
|
|
|
|
if (ifindex == ifp->ifindex)
|
|
|
|
return ifp;
|
|
|
|
} else
|
|
|
|
return ifp;
|
|
|
|
}
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
return NULL;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
struct interface *if_lookup_by_ipv6_exact(struct in6_addr *addr,
|
|
|
|
ifindex_t ifindex, vrf_id_t vrf_id)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-10-03 03:06:01 +02:00
|
|
|
struct vrf *vrf;
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *cnode;
|
|
|
|
struct interface *ifp;
|
|
|
|
struct connected *connected;
|
|
|
|
struct prefix *cp;
|
|
|
|
|
2017-10-03 03:06:01 +02:00
|
|
|
vrf = vrf_lookup_by_id(vrf_id);
|
|
|
|
if (!vrf)
|
|
|
|
return NULL;
|
|
|
|
|
2017-10-06 20:25:58 +02:00
|
|
|
FOR_ALL_INTERFACES (vrf, ifp) {
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS_RO(ifp->connected, cnode, connected)) {
|
|
|
|
cp = connected->address;
|
|
|
|
|
|
|
|
if (cp->family == AF_INET6)
|
|
|
|
if (IPV6_ADDR_SAME(&cp->u.prefix6, addr)) {
|
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(
|
|
|
|
&cp->u.prefix6)) {
|
|
|
|
if (ifindex == ifp->ifindex)
|
|
|
|
return ifp;
|
|
|
|
} else
|
|
|
|
return ifp;
|
|
|
|
}
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
return NULL;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int if_get_ipv6_global(struct interface *ifp, struct in6_addr *addr)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *cnode;
|
|
|
|
struct connected *connected;
|
|
|
|
struct prefix *cp;
|
|
|
|
|
|
|
|
for (ALL_LIST_ELEMENTS_RO(ifp->connected, cnode, connected)) {
|
|
|
|
cp = connected->address;
|
|
|
|
|
|
|
|
if (cp->family == AF_INET6)
|
|
|
|
if (!IN6_IS_ADDR_LINKLOCAL(&cp->u.prefix6)) {
|
|
|
|
memcpy(addr, &cp->u.prefix6, IPV6_MAX_BYTELEN);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int if_get_ipv6_local(struct interface *ifp, struct in6_addr *addr)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *cnode;
|
|
|
|
struct connected *connected;
|
|
|
|
struct prefix *cp;
|
|
|
|
|
|
|
|
for (ALL_LIST_ELEMENTS_RO(ifp->connected, cnode, connected)) {
|
|
|
|
cp = connected->address;
|
|
|
|
|
|
|
|
if (cp->family == AF_INET6)
|
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(&cp->u.prefix6)) {
|
|
|
|
memcpy(addr, &cp->u.prefix6, IPV6_MAX_BYTELEN);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int if_get_ipv4_address(struct interface *ifp, struct in_addr *addr)
|
2014-01-12 19:30:13 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct listnode *cnode;
|
|
|
|
struct connected *connected;
|
|
|
|
struct prefix *cp;
|
|
|
|
|
|
|
|
for (ALL_LIST_ELEMENTS_RO(ifp->connected, cnode, connected)) {
|
|
|
|
cp = connected->address;
|
|
|
|
if ((cp->family == AF_INET)
|
|
|
|
&& !ipv4_martian(&(cp->u.prefix4))) {
|
|
|
|
*addr = cp->u.prefix4;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return 0;
|
2014-01-12 19:30:13 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
int bgp_nexthop_set(union sockunion *local, union sockunion *remote,
|
|
|
|
struct bgp_nexthop *nexthop, struct peer *peer)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
int ret = 0;
|
|
|
|
struct interface *ifp = NULL;
|
|
|
|
|
|
|
|
memset(nexthop, 0, sizeof(struct bgp_nexthop));
|
|
|
|
|
|
|
|
if (!local)
|
|
|
|
return -1;
|
|
|
|
if (!remote)
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
if (local->sa.sa_family == AF_INET) {
|
|
|
|
nexthop->v4 = local->sin.sin_addr;
|
|
|
|
if (peer->update_if)
|
|
|
|
ifp = if_lookup_by_name(peer->update_if,
|
|
|
|
peer->bgp->vrf_id);
|
|
|
|
else
|
|
|
|
ifp = if_lookup_by_ipv4_exact(&local->sin.sin_addr,
|
|
|
|
peer->bgp->vrf_id);
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
if (local->sa.sa_family == AF_INET6) {
|
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(&local->sin6.sin6_addr)) {
|
|
|
|
if (peer->conf_if || peer->ifname)
|
|
|
|
ifp = if_lookup_by_name(peer->conf_if
|
|
|
|
? peer->conf_if
|
|
|
|
: peer->ifname,
|
|
|
|
peer->bgp->vrf_id);
|
|
|
|
} else if (peer->update_if)
|
|
|
|
ifp = if_lookup_by_name(peer->update_if,
|
|
|
|
peer->bgp->vrf_id);
|
|
|
|
else
|
|
|
|
ifp = if_lookup_by_ipv6_exact(&local->sin6.sin6_addr,
|
|
|
|
local->sin6.sin6_scope_id,
|
|
|
|
peer->bgp->vrf_id);
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
|
|
|
|
if (!ifp)
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
nexthop->ifp = ifp;
|
|
|
|
|
|
|
|
/* IPv4 connection, fetch and store IPv6 local address(es) if any. */
|
|
|
|
if (local->sa.sa_family == AF_INET) {
|
|
|
|
/* IPv6 nexthop*/
|
|
|
|
ret = if_get_ipv6_global(ifp, &nexthop->v6_global);
|
|
|
|
|
|
|
|
if (!ret) {
|
|
|
|
/* There is no global nexthop. Use link-local address as
|
|
|
|
* both the
|
|
|
|
* global and link-local nexthop. In this scenario, the
|
|
|
|
* expectation
|
|
|
|
* for interop is that the network admin would use a
|
|
|
|
* route-map to
|
|
|
|
* specify the global IPv6 nexthop.
|
|
|
|
*/
|
|
|
|
if_get_ipv6_local(ifp, &nexthop->v6_global);
|
|
|
|
memcpy(&nexthop->v6_local, &nexthop->v6_global,
|
|
|
|
IPV6_MAX_BYTELEN);
|
|
|
|
} else
|
|
|
|
if_get_ipv6_local(ifp, &nexthop->v6_local);
|
|
|
|
|
|
|
|
if (if_lookup_by_ipv4(&remote->sin.sin_addr, peer->bgp->vrf_id))
|
|
|
|
peer->shared_network = 1;
|
|
|
|
else
|
|
|
|
peer->shared_network = 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* IPv6 connection, fetch and store IPv4 local address if any. */
|
|
|
|
if (local->sa.sa_family == AF_INET6) {
|
|
|
|
struct interface *direct = NULL;
|
|
|
|
|
|
|
|
/* IPv4 nexthop. */
|
|
|
|
ret = if_get_ipv4_address(ifp, &nexthop->v4);
|
|
|
|
if (!ret && peer->local_id.s_addr)
|
|
|
|
nexthop->v4 = peer->local_id;
|
|
|
|
|
|
|
|
/* Global address*/
|
|
|
|
if (!IN6_IS_ADDR_LINKLOCAL(&local->sin6.sin6_addr)) {
|
|
|
|
memcpy(&nexthop->v6_global, &local->sin6.sin6_addr,
|
|
|
|
IPV6_MAX_BYTELEN);
|
|
|
|
|
|
|
|
/* If directory connected set link-local address. */
|
|
|
|
direct = if_lookup_by_ipv6(&remote->sin6.sin6_addr,
|
|
|
|
remote->sin6.sin6_scope_id,
|
|
|
|
peer->bgp->vrf_id);
|
|
|
|
if (direct)
|
|
|
|
if_get_ipv6_local(ifp, &nexthop->v6_local);
|
|
|
|
} else
|
|
|
|
/* Link-local address. */
|
|
|
|
{
|
|
|
|
ret = if_get_ipv6_global(ifp, &nexthop->v6_global);
|
|
|
|
|
|
|
|
/* If there is no global address. Set link-local
|
|
|
|
address as
|
|
|
|
global. I know this break RFC specification... */
|
|
|
|
/* In this scenario, the expectation for interop is that
|
|
|
|
* the
|
|
|
|
* network admin would use a route-map to specify the
|
|
|
|
* global
|
|
|
|
* IPv6 nexthop.
|
|
|
|
*/
|
|
|
|
if (!ret)
|
|
|
|
memcpy(&nexthop->v6_global,
|
|
|
|
&local->sin6.sin6_addr,
|
|
|
|
IPV6_MAX_BYTELEN);
|
|
|
|
/* Always set the link-local address */
|
|
|
|
memcpy(&nexthop->v6_local, &local->sin6.sin6_addr,
|
|
|
|
IPV6_MAX_BYTELEN);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(&local->sin6.sin6_addr)
|
|
|
|
|| if_lookup_by_ipv6(&remote->sin6.sin6_addr,
|
|
|
|
remote->sin6.sin6_scope_id,
|
|
|
|
peer->bgp->vrf_id))
|
|
|
|
peer->shared_network = 1;
|
|
|
|
else
|
|
|
|
peer->shared_network = 0;
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* KAME stack specific treatment. */
|
2002-12-13 21:15:29 +01:00
|
|
|
#ifdef KAME
|
2017-07-17 14:03:14 +02:00
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(&nexthop->v6_global)
|
|
|
|
&& IN6_LINKLOCAL_IFINDEX(nexthop->v6_global)) {
|
|
|
|
SET_IN6_LINKLOCAL_IFINDEX(nexthop->v6_global, 0);
|
|
|
|
}
|
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(&nexthop->v6_local)
|
|
|
|
&& IN6_LINKLOCAL_IFINDEX(nexthop->v6_local)) {
|
|
|
|
SET_IN6_LINKLOCAL_IFINDEX(nexthop->v6_local, 0);
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
#endif /* KAME */
|
2015-08-29 20:40:32 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* If we have identified the local interface, there is no error for now.
|
|
|
|
*/
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2018-04-05 19:42:27 +02:00
|
|
|
static struct in6_addr *bgp_info_to_ipv6_nexthop(struct bgp_info *info,
|
|
|
|
ifindex_t *ifindex)
|
bgpd: bgpd-table-map.patch
COMMAND:
table-map <route-map-name>
DESCRIPTION:
This feature is used to apply a route-map on route updates from BGP to Zebra.
All the applicable match operations are allowed, such as match on prefix,
next-hop, communities, etc. Set operations for this attach-point are limited
to metric and next-hop only. Any operation of this feature does not affect
BGPs internal RIB.
Supported for ipv4 and ipv6 address families. It works on multi-paths as well,
however, metric setting is based on the best-path only.
IMPLEMENTATION NOTES:
The route-map application at this point is not supposed to modify any of BGP
route's attributes (anything in bgp_info for that matter). To achieve that,
creating a copy of the bgp_attr was inevitable. Implementation tries to keep
the memory footprint low, code comments do point out the rationale behind a
few choices made.
bgp_zebra_announce() was already a big routine, adding this feature would
extend it further. Patch has created a few smaller routines/macros whereever
possible to keep the size of the routine in check without compromising on the
readability of the code/flow inside this routine.
For updating a partially filtered route (with its nexthops), BGP to Zebra
replacement semantic of the next-hops serves the purpose well. However, with
this patch there could be some redundant withdraws each time BGP announces a
route thats (all the nexthops) gets denied by the route-map application.
Handling of this case could be optimized by keeping state with the prefix and
the nexthops in BGP. The patch doesn't optimizing that case, as even with the
redundant withdraws the total number of updates to zebra are still be capped
by the total number of routes in the table.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Pradosh Mohapatra <pmohapat@cumulusnetworks.com>
2015-05-20 02:40:34 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct in6_addr *nexthop = NULL;
|
|
|
|
|
|
|
|
/* Only global address nexthop exists. */
|
2018-04-05 19:42:27 +02:00
|
|
|
if (info->attr->mp_nexthop_len == BGP_ATTR_NHLEN_IPV6_GLOBAL) {
|
2017-07-17 14:03:14 +02:00
|
|
|
nexthop = &info->attr->mp_nexthop_global;
|
2018-04-05 19:42:27 +02:00
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(nexthop))
|
|
|
|
*ifindex = info->attr->nh_ifindex;
|
|
|
|
|
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
|
|
|
|
/* If both global and link-local address present. */
|
|
|
|
if (info->attr->mp_nexthop_len == BGP_ATTR_NHLEN_IPV6_GLOBAL_AND_LL) {
|
|
|
|
/* Check if route-map is set to prefer global over link-local */
|
2018-04-05 19:42:27 +02:00
|
|
|
if (info->attr->mp_nexthop_prefer_global) {
|
2017-07-17 14:03:14 +02:00
|
|
|
nexthop = &info->attr->mp_nexthop_global;
|
2018-04-05 19:42:27 +02:00
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(nexthop))
|
|
|
|
*ifindex = info->attr->nh_ifindex;
|
|
|
|
} else {
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Workaround for Cisco's nexthop bug. */
|
|
|
|
if (IN6_IS_ADDR_UNSPECIFIED(
|
|
|
|
&info->attr->mp_nexthop_global)
|
2018-04-12 14:59:08 +02:00
|
|
|
&& info->peer->su_remote->sa.sa_family
|
|
|
|
== AF_INET6) {
|
2017-07-17 14:03:14 +02:00
|
|
|
nexthop =
|
|
|
|
&info->peer->su_remote->sin6.sin6_addr;
|
2018-04-05 19:42:27 +02:00
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(nexthop))
|
2018-04-12 14:59:08 +02:00
|
|
|
*ifindex = info->peer->nexthop.ifp
|
|
|
|
->ifindex;
|
2018-04-05 19:42:27 +02:00
|
|
|
} else {
|
2017-07-17 14:03:14 +02:00
|
|
|
nexthop = &info->attr->mp_nexthop_local;
|
2018-04-05 19:42:27 +02:00
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(nexthop))
|
|
|
|
*ifindex = info->attr->nh_lla_ifindex;
|
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return nexthop;
|
bgpd: bgpd-table-map.patch
COMMAND:
table-map <route-map-name>
DESCRIPTION:
This feature is used to apply a route-map on route updates from BGP to Zebra.
All the applicable match operations are allowed, such as match on prefix,
next-hop, communities, etc. Set operations for this attach-point are limited
to metric and next-hop only. Any operation of this feature does not affect
BGPs internal RIB.
Supported for ipv4 and ipv6 address families. It works on multi-paths as well,
however, metric setting is based on the best-path only.
IMPLEMENTATION NOTES:
The route-map application at this point is not supposed to modify any of BGP
route's attributes (anything in bgp_info for that matter). To achieve that,
creating a copy of the bgp_attr was inevitable. Implementation tries to keep
the memory footprint low, code comments do point out the rationale behind a
few choices made.
bgp_zebra_announce() was already a big routine, adding this feature would
extend it further. Patch has created a few smaller routines/macros whereever
possible to keep the size of the routine in check without compromising on the
readability of the code/flow inside this routine.
For updating a partially filtered route (with its nexthops), BGP to Zebra
replacement semantic of the next-hops serves the purpose well. However, with
this patch there could be some redundant withdraws each time BGP announces a
route thats (all the nexthops) gets denied by the route-map application.
Handling of this case could be optimized by keeping state with the prefix and
the nexthops in BGP. The patch doesn't optimizing that case, as even with the
redundant withdraws the total number of updates to zebra are still be capped
by the total number of routes in the table.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Pradosh Mohapatra <pmohapat@cumulusnetworks.com>
2015-05-20 02:40:34 +02:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_table_map_apply(struct route_map *map, struct prefix *p,
|
|
|
|
struct bgp_info *info)
|
bgpd: bgpd-table-map.patch
COMMAND:
table-map <route-map-name>
DESCRIPTION:
This feature is used to apply a route-map on route updates from BGP to Zebra.
All the applicable match operations are allowed, such as match on prefix,
next-hop, communities, etc. Set operations for this attach-point are limited
to metric and next-hop only. Any operation of this feature does not affect
BGPs internal RIB.
Supported for ipv4 and ipv6 address families. It works on multi-paths as well,
however, metric setting is based on the best-path only.
IMPLEMENTATION NOTES:
The route-map application at this point is not supposed to modify any of BGP
route's attributes (anything in bgp_info for that matter). To achieve that,
creating a copy of the bgp_attr was inevitable. Implementation tries to keep
the memory footprint low, code comments do point out the rationale behind a
few choices made.
bgp_zebra_announce() was already a big routine, adding this feature would
extend it further. Patch has created a few smaller routines/macros whereever
possible to keep the size of the routine in check without compromising on the
readability of the code/flow inside this routine.
For updating a partially filtered route (with its nexthops), BGP to Zebra
replacement semantic of the next-hops serves the purpose well. However, with
this patch there could be some redundant withdraws each time BGP announces a
route thats (all the nexthops) gets denied by the route-map application.
Handling of this case could be optimized by keeping state with the prefix and
the nexthops in BGP. The patch doesn't optimizing that case, as even with the
redundant withdraws the total number of updates to zebra are still be capped
by the total number of routes in the table.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Pradosh Mohapatra <pmohapat@cumulusnetworks.com>
2015-05-20 02:40:34 +02:00
|
|
|
{
|
2017-09-07 15:19:06 +02:00
|
|
|
route_map_result_t ret;
|
|
|
|
|
|
|
|
ret = route_map_apply(map, p, RMAP_BGP, info);
|
|
|
|
bgp_attr_flush(info->attr);
|
|
|
|
|
|
|
|
if (ret != RMAP_DENYMATCH)
|
2017-07-17 14:03:14 +02:00
|
|
|
return 1;
|
|
|
|
|
|
|
|
if (bgp_debug_zebra(p)) {
|
|
|
|
if (p->family == AF_INET) {
|
|
|
|
char buf[2][INET_ADDRSTRLEN];
|
|
|
|
zlog_debug(
|
|
|
|
"Zebra rmap deny: IPv4 route %s/%d nexthop %s",
|
|
|
|
inet_ntop(AF_INET, &p->u.prefix4, buf[0],
|
|
|
|
sizeof(buf[0])),
|
|
|
|
p->prefixlen,
|
|
|
|
inet_ntop(AF_INET, &info->attr->nexthop, buf[1],
|
|
|
|
sizeof(buf[1])));
|
|
|
|
}
|
|
|
|
if (p->family == AF_INET6) {
|
|
|
|
char buf[2][INET6_ADDRSTRLEN];
|
2018-04-05 19:42:27 +02:00
|
|
|
ifindex_t ifindex;
|
|
|
|
struct in6_addr *nexthop;
|
|
|
|
|
|
|
|
nexthop = bgp_info_to_ipv6_nexthop(info, &ifindex);
|
2017-07-17 14:03:14 +02:00
|
|
|
zlog_debug(
|
|
|
|
"Zebra rmap deny: IPv6 route %s/%d nexthop %s",
|
|
|
|
inet_ntop(AF_INET6, &p->u.prefix6, buf[0],
|
|
|
|
sizeof(buf[0])),
|
|
|
|
p->prefixlen,
|
2018-04-05 19:42:27 +02:00
|
|
|
inet_ntop(AF_INET6, nexthop,
|
2017-07-17 14:03:14 +02:00
|
|
|
buf[1], sizeof(buf[1])));
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return 0;
|
bgpd: bgpd-table-map.patch
COMMAND:
table-map <route-map-name>
DESCRIPTION:
This feature is used to apply a route-map on route updates from BGP to Zebra.
All the applicable match operations are allowed, such as match on prefix,
next-hop, communities, etc. Set operations for this attach-point are limited
to metric and next-hop only. Any operation of this feature does not affect
BGPs internal RIB.
Supported for ipv4 and ipv6 address families. It works on multi-paths as well,
however, metric setting is based on the best-path only.
IMPLEMENTATION NOTES:
The route-map application at this point is not supposed to modify any of BGP
route's attributes (anything in bgp_info for that matter). To achieve that,
creating a copy of the bgp_attr was inevitable. Implementation tries to keep
the memory footprint low, code comments do point out the rationale behind a
few choices made.
bgp_zebra_announce() was already a big routine, adding this feature would
extend it further. Patch has created a few smaller routines/macros whereever
possible to keep the size of the routine in check without compromising on the
readability of the code/flow inside this routine.
For updating a partially filtered route (with its nexthops), BGP to Zebra
replacement semantic of the next-hops serves the purpose well. However, with
this patch there could be some redundant withdraws each time BGP announces a
route thats (all the nexthops) gets denied by the route-map application.
Handling of this case could be optimized by keeping state with the prefix and
the nexthops in BGP. The patch doesn't optimizing that case, as even with the
redundant withdraws the total number of updates to zebra are still be capped
by the total number of routes in the table.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Pradosh Mohapatra <pmohapat@cumulusnetworks.com>
2015-05-20 02:40:34 +02:00
|
|
|
}
|
|
|
|
|
2018-03-05 18:09:57 +01:00
|
|
|
static struct thread *bgp_tm_thread_connect;
|
|
|
|
static bool bgp_tm_status_connected;
|
2018-04-03 15:06:50 +02:00
|
|
|
static bool bgp_tm_chunk_obtained;
|
|
|
|
#define BGP_FLOWSPEC_TABLE_CHUNK 100000
|
|
|
|
static uint32_t bgp_tm_min, bgp_tm_max, bgp_tm_chunk_size;
|
2018-05-23 14:14:53 +02:00
|
|
|
struct bgp *bgp_tm_bgp;
|
2018-03-05 18:09:57 +01:00
|
|
|
|
|
|
|
static int bgp_zebra_tm_connect(struct thread *t)
|
|
|
|
{
|
|
|
|
struct zclient *zclient;
|
|
|
|
int delay = 10, ret = 0;
|
|
|
|
|
|
|
|
zclient = THREAD_ARG(t);
|
|
|
|
if (bgp_tm_status_connected && zclient->sock > 0)
|
|
|
|
delay = 60;
|
|
|
|
else {
|
|
|
|
bgp_tm_status_connected = false;
|
|
|
|
ret = tm_table_manager_connect(zclient);
|
|
|
|
}
|
|
|
|
if (ret < 0) {
|
|
|
|
zlog_warn("Error connecting to table manager!");
|
|
|
|
bgp_tm_status_connected = false;
|
|
|
|
} else {
|
|
|
|
if (!bgp_tm_status_connected)
|
|
|
|
zlog_debug("Connecting to table manager. Success");
|
|
|
|
bgp_tm_status_connected = true;
|
2018-04-03 15:06:50 +02:00
|
|
|
if (!bgp_tm_chunk_obtained) {
|
|
|
|
if (bgp_zebra_get_table_range(bgp_tm_chunk_size,
|
|
|
|
&bgp_tm_min,
|
2018-05-23 14:14:53 +02:00
|
|
|
&bgp_tm_max) >= 0) {
|
2018-04-03 15:06:50 +02:00
|
|
|
bgp_tm_chunk_obtained = true;
|
2018-05-23 14:14:53 +02:00
|
|
|
/* parse non installed entries */
|
|
|
|
bgp_zebra_announce_table(bgp_tm_bgp, AFI_IP, SAFI_FLOWSPEC);
|
|
|
|
}
|
2018-04-03 15:06:50 +02:00
|
|
|
}
|
2018-03-05 18:09:57 +01:00
|
|
|
}
|
|
|
|
thread_add_timer(bm->master, bgp_zebra_tm_connect, zclient, delay,
|
|
|
|
&bgp_tm_thread_connect);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-05-23 14:14:53 +02:00
|
|
|
bool bgp_zebra_tm_chunk_obtained(void)
|
|
|
|
{
|
|
|
|
return bgp_tm_chunk_obtained;
|
|
|
|
}
|
|
|
|
|
2018-04-03 15:06:50 +02:00
|
|
|
uint32_t bgp_zebra_tm_get_id(void)
|
|
|
|
{
|
|
|
|
static int table_id;
|
|
|
|
|
|
|
|
if (!bgp_tm_chunk_obtained)
|
|
|
|
return ++table_id;
|
|
|
|
return bgp_tm_min++;
|
|
|
|
}
|
|
|
|
|
2018-05-23 14:14:53 +02:00
|
|
|
void bgp_zebra_init_tm_connect(struct bgp *bgp)
|
2018-03-05 18:09:57 +01:00
|
|
|
{
|
|
|
|
int delay = 1;
|
|
|
|
|
|
|
|
/* if already set, do nothing
|
|
|
|
*/
|
|
|
|
if (bgp_tm_thread_connect != NULL)
|
|
|
|
return;
|
|
|
|
bgp_tm_status_connected = false;
|
2018-04-03 15:06:50 +02:00
|
|
|
bgp_tm_chunk_obtained = false;
|
|
|
|
bgp_tm_min = bgp_tm_max = 0;
|
|
|
|
bgp_tm_chunk_size = BGP_FLOWSPEC_TABLE_CHUNK;
|
2018-05-23 14:14:53 +02:00
|
|
|
bgp_tm_bgp = bgp;
|
2018-03-05 18:09:57 +01:00
|
|
|
thread_add_timer(bm->master, bgp_zebra_tm_connect, zclient, delay,
|
|
|
|
&bgp_tm_thread_connect);
|
|
|
|
}
|
|
|
|
|
|
|
|
int bgp_zebra_get_table_range(uint32_t chunk_size,
|
|
|
|
uint32_t *start, uint32_t *end)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (!bgp_tm_status_connected)
|
|
|
|
return -1;
|
|
|
|
ret = tm_get_table_chunk(zclient, chunk_size, start, end);
|
|
|
|
if (ret < 0) {
|
|
|
|
zlog_err("BGP: Error getting table chunk %u", chunk_size);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
zlog_info("BGP: Table Manager returns range from chunk %u is [%u %u]",
|
|
|
|
chunk_size, *start, *end);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-04-05 19:42:27 +02:00
|
|
|
static int update_ipv4nh_for_route_install(int nh_othervrf,
|
|
|
|
struct in_addr *nexthop,
|
|
|
|
struct attr *attr,
|
|
|
|
bool is_evpn,
|
|
|
|
struct zapi_nexthop *api_nh)
|
|
|
|
{
|
|
|
|
api_nh->gate.ipv4 = *nexthop;
|
|
|
|
|
|
|
|
/* Need to set fields appropriately for EVPN routes imported into
|
|
|
|
* a VRF (which are programmed as onlink on l3-vni SVI) as well as
|
|
|
|
* connected routes leaked into a VRF.
|
|
|
|
*/
|
|
|
|
if (is_evpn)
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IPV4_IFINDEX;
|
|
|
|
else if (nh_othervrf &&
|
|
|
|
api_nh->gate.ipv4.s_addr == INADDR_ANY) {
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IFINDEX;
|
|
|
|
api_nh->ifindex = attr->nh_ifindex;
|
|
|
|
} else
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IPV4;
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int update_ipv6nh_for_route_install(int nh_othervrf,
|
|
|
|
struct in6_addr *nexthop,
|
|
|
|
ifindex_t ifindex,
|
|
|
|
struct bgp_info *ri,
|
|
|
|
struct bgp_info *best_ri,
|
|
|
|
bool is_evpn,
|
|
|
|
struct zapi_nexthop *api_nh)
|
|
|
|
{
|
|
|
|
struct attr *attr;
|
|
|
|
|
|
|
|
attr = ri->attr;
|
|
|
|
|
|
|
|
if (is_evpn)
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IPV6_IFINDEX;
|
|
|
|
else if (nh_othervrf) {
|
|
|
|
if (IN6_IS_ADDR_UNSPECIFIED(nexthop)) {
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IFINDEX;
|
|
|
|
api_nh->ifindex = attr->nh_ifindex;
|
|
|
|
} else if (IN6_IS_ADDR_LINKLOCAL(nexthop)) {
|
|
|
|
if (ifindex == 0)
|
|
|
|
return 0;
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IPV6_IFINDEX;
|
|
|
|
api_nh->ifindex = ifindex;
|
|
|
|
} else {
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IPV6;
|
|
|
|
api_nh->ifindex = 0;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
if (IN6_IS_ADDR_LINKLOCAL(nexthop)) {
|
|
|
|
if (ri == best_ri &&
|
|
|
|
attr->mp_nexthop_len
|
|
|
|
== BGP_ATTR_NHLEN_IPV6_GLOBAL_AND_LL)
|
|
|
|
if (ri->peer->nexthop.ifp)
|
|
|
|
ifindex = ri->peer->nexthop.ifp
|
|
|
|
->ifindex;
|
|
|
|
if (!ifindex) {
|
|
|
|
if (ri->peer->conf_if)
|
|
|
|
ifindex = ri->peer->ifp->ifindex;
|
|
|
|
else if (ri->peer->ifname)
|
|
|
|
ifindex = ifname2ifindex(
|
|
|
|
ri->peer->ifname,
|
|
|
|
ri->peer->bgp->vrf_id);
|
|
|
|
else if (ri->peer->nexthop.ifp)
|
|
|
|
ifindex = ri->peer->nexthop.ifp
|
|
|
|
->ifindex;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ifindex == 0)
|
|
|
|
return 0;
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IPV6_IFINDEX;
|
|
|
|
api_nh->ifindex = ifindex;
|
|
|
|
} else {
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IPV6;
|
|
|
|
api_nh->ifindex = 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
api_nh->gate.ipv6 = *nexthop;
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zebra_announce(struct bgp_node *rn, struct prefix *p,
|
|
|
|
struct bgp_info *info, struct bgp *bgp, afi_t afi,
|
|
|
|
safi_t safi)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-08-21 02:19:25 +02:00
|
|
|
struct zapi_route api;
|
|
|
|
struct zapi_nexthop *api_nh;
|
2017-08-21 02:36:44 +02:00
|
|
|
int nh_family;
|
2017-09-21 14:49:31 +02:00
|
|
|
unsigned int valid_nh_count = 0;
|
2017-08-21 02:36:44 +02:00
|
|
|
int has_valid_label = 0;
|
2018-03-27 21:13:34 +02:00
|
|
|
uint8_t distance;
|
2017-07-17 14:03:14 +02:00
|
|
|
struct peer *peer;
|
|
|
|
struct bgp_info *mpinfo;
|
2018-03-27 21:13:34 +02:00
|
|
|
uint32_t metric;
|
2017-09-07 15:19:06 +02:00
|
|
|
struct attr local_attr;
|
2017-07-17 14:03:14 +02:00
|
|
|
struct bgp_info local_info;
|
2017-09-07 15:19:06 +02:00
|
|
|
struct bgp_info *mpinfo_cp = &local_info;
|
2017-07-17 14:03:14 +02:00
|
|
|
route_tag_t tag;
|
|
|
|
mpls_label_t label;
|
2018-03-09 21:52:55 +01:00
|
|
|
int nh_othervrf = 0;
|
2018-03-24 00:57:03 +01:00
|
|
|
char buf_prefix[PREFIX_STRLEN]; /* filled in if we are debugging */
|
2018-04-05 19:42:27 +02:00
|
|
|
bool is_evpn = false;
|
|
|
|
int nh_updated;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
|
|
|
/* Don't try to install if we're not connected to Zebra or Zebra doesn't
|
|
|
|
* know of this instance.
|
|
|
|
*/
|
|
|
|
if (!bgp_install_info_to_zebra(bgp))
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (bgp->main_zebra_update_hold)
|
|
|
|
return;
|
|
|
|
|
2018-03-24 00:57:03 +01:00
|
|
|
if (bgp_debug_zebra(p))
|
2018-05-22 15:53:01 +02:00
|
|
|
prefix2str(p, buf_prefix, sizeof(buf_prefix));
|
2018-03-24 00:57:03 +01:00
|
|
|
|
2018-01-26 18:36:24 +01:00
|
|
|
if (safi == SAFI_FLOWSPEC)
|
|
|
|
return bgp_pbr_update_entry(bgp, &rn->p,
|
|
|
|
info, afi, safi, true);
|
|
|
|
|
2018-03-09 21:52:55 +01:00
|
|
|
/*
|
|
|
|
* vrf leaking support (will have only one nexthop)
|
|
|
|
*/
|
|
|
|
if (info->extra && info->extra->bgp_orig)
|
|
|
|
nh_othervrf = 1;
|
|
|
|
|
2017-08-21 02:19:25 +02:00
|
|
|
/* Make Zebra API structure. */
|
|
|
|
memset(&api, 0, sizeof(api));
|
|
|
|
api.vrf_id = bgp->vrf_id;
|
|
|
|
api.type = ZEBRA_ROUTE_BGP;
|
|
|
|
api.safi = safi;
|
|
|
|
api.prefix = *p;
|
|
|
|
SET_FLAG(api.message, ZAPI_MESSAGE_NEXTHOP);
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
peer = info->peer;
|
|
|
|
|
2018-03-09 21:52:55 +01:00
|
|
|
if (info->type == ZEBRA_ROUTE_BGP
|
|
|
|
&& info->sub_type == BGP_ROUTE_IMPORTED) {
|
|
|
|
|
2018-03-29 07:11:30 +02:00
|
|
|
/* Obtain peer from parent */
|
|
|
|
if (info->extra && info->extra->parent)
|
|
|
|
peer = ((struct bgp_info *)(info->extra->parent))->peer;
|
2018-03-09 21:52:55 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
tag = info->attr->tag;
|
|
|
|
|
2018-03-30 02:24:00 +02:00
|
|
|
/* If the route's source is EVPN, flag as such. */
|
2018-04-05 19:42:27 +02:00
|
|
|
is_evpn = is_route_parent_evpn(info);
|
|
|
|
if (is_evpn)
|
2017-11-07 10:52:23 +01:00
|
|
|
SET_FLAG(api.flags, ZEBRA_FLAG_EVPN_ROUTE);
|
2017-10-11 10:32:54 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (peer->sort == BGP_PEER_IBGP || peer->sort == BGP_PEER_CONFED
|
|
|
|
|| info->sub_type == BGP_ROUTE_AGGREGATE) {
|
2017-08-21 02:19:25 +02:00
|
|
|
SET_FLAG(api.flags, ZEBRA_FLAG_IBGP);
|
2018-02-27 03:26:33 +01:00
|
|
|
SET_FLAG(api.flags, ZEBRA_FLAG_ALLOW_RECURSION);
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if ((peer->sort == BGP_PEER_EBGP && peer->ttl != 1)
|
|
|
|
|| CHECK_FLAG(peer->flags, PEER_FLAG_DISABLE_CONNECTED_CHECK)
|
|
|
|
|| bgp_flag_check(bgp, BGP_FLAG_DISABLE_NH_CONNECTED_CHK))
|
|
|
|
|
2018-02-27 03:26:33 +01:00
|
|
|
SET_FLAG(api.flags, ZEBRA_FLAG_ALLOW_RECURSION);
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
/* Metric is currently based on the best-path only */
|
|
|
|
metric = info->attr->med;
|
|
|
|
for (mpinfo = info; mpinfo; mpinfo = bgp_info_mpath_next(mpinfo)) {
|
2017-09-21 14:49:31 +02:00
|
|
|
if (valid_nh_count >= multipath_num)
|
|
|
|
break;
|
|
|
|
|
2017-09-07 15:19:06 +02:00
|
|
|
*mpinfo_cp = *mpinfo;
|
|
|
|
|
2017-09-19 14:33:40 +02:00
|
|
|
/* Get nexthop address-family */
|
|
|
|
if (p->family == AF_INET
|
|
|
|
&& !BGP_ATTR_NEXTHOP_AFI_IP6(mpinfo_cp->attr))
|
|
|
|
nh_family = AF_INET;
|
|
|
|
else if (p->family == AF_INET6
|
|
|
|
|| (p->family == AF_INET
|
|
|
|
&& BGP_ATTR_NEXTHOP_AFI_IP6(mpinfo_cp->attr)))
|
|
|
|
nh_family = AF_INET6;
|
|
|
|
else
|
|
|
|
continue;
|
|
|
|
|
2018-03-01 01:10:02 +01:00
|
|
|
api_nh = &api.nexthops[valid_nh_count];
|
2018-03-16 21:16:31 +01:00
|
|
|
api_nh->vrf_id = nh_othervrf ? info->extra->bgp_orig->vrf_id
|
|
|
|
: bgp->vrf_id;
|
2017-08-21 02:36:44 +02:00
|
|
|
if (nh_family == AF_INET) {
|
2018-03-09 21:52:55 +01:00
|
|
|
if (bgp_debug_zebra(&api.prefix)) {
|
|
|
|
if (mpinfo->extra) {
|
|
|
|
zlog_debug(
|
|
|
|
"%s: p=%s, bgp_is_valid_label: %d",
|
|
|
|
__func__, buf_prefix,
|
|
|
|
bgp_is_valid_label(
|
|
|
|
&mpinfo->extra
|
|
|
|
->label[0]));
|
|
|
|
} else {
|
|
|
|
zlog_debug(
|
|
|
|
"%s: p=%s, extra is NULL, no label",
|
|
|
|
__func__, buf_prefix);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-04-06 18:31:11 +02:00
|
|
|
if (bgp->table_map[afi][safi].name) {
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Copy info and attributes, so the route-map
|
2017-09-07 15:19:06 +02:00
|
|
|
apply doesn't modify the BGP route info. */
|
|
|
|
local_attr = *mpinfo->attr;
|
|
|
|
mpinfo_cp->attr = &local_attr;
|
2018-03-09 21:52:55 +01:00
|
|
|
}
|
2017-09-07 15:19:06 +02:00
|
|
|
|
2018-03-09 21:52:55 +01:00
|
|
|
if (bgp->table_map[afi][safi].name) {
|
2017-09-07 15:19:06 +02:00
|
|
|
if (!bgp_table_map_apply(
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp->table_map[afi][safi].map, p,
|
2017-09-07 15:19:06 +02:00
|
|
|
mpinfo_cp))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
/* metric/tag is only allowed to be
|
|
|
|
* overridden on 1st nexthop */
|
|
|
|
if (mpinfo == info) {
|
|
|
|
metric = mpinfo_cp->attr->med;
|
|
|
|
tag = mpinfo_cp->attr->tag;
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
2017-09-07 15:19:06 +02:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2018-04-05 19:42:27 +02:00
|
|
|
nh_updated = update_ipv4nh_for_route_install(
|
|
|
|
nh_othervrf,
|
|
|
|
&mpinfo_cp->attr->nexthop,
|
|
|
|
mpinfo_cp->attr, is_evpn, api_nh);
|
2017-08-21 02:36:44 +02:00
|
|
|
} else {
|
|
|
|
ifindex_t ifindex;
|
|
|
|
struct in6_addr *nexthop;
|
2017-08-21 02:19:25 +02:00
|
|
|
|
2018-04-06 18:31:11 +02:00
|
|
|
if (bgp->table_map[afi][safi].name) {
|
2018-03-09 21:52:55 +01:00
|
|
|
/* Copy info and attributes, so the route-map
|
|
|
|
apply doesn't modify the BGP route info. */
|
|
|
|
local_attr = *mpinfo->attr;
|
|
|
|
mpinfo_cp->attr = &local_attr;
|
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (bgp->table_map[afi][safi].name) {
|
|
|
|
/* Copy info and attributes, so the route-map
|
2017-09-07 15:19:06 +02:00
|
|
|
apply doesn't modify the BGP route info. */
|
|
|
|
local_attr = *mpinfo->attr;
|
|
|
|
mpinfo_cp->attr = &local_attr;
|
|
|
|
|
|
|
|
if (!bgp_table_map_apply(
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp->table_map[afi][safi].map, p,
|
2017-09-07 15:19:06 +02:00
|
|
|
mpinfo_cp))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
/* metric/tag is only allowed to be
|
|
|
|
* overridden on 1st nexthop */
|
|
|
|
if (mpinfo == info) {
|
|
|
|
metric = mpinfo_cp->attr->med;
|
|
|
|
tag = mpinfo_cp->attr->tag;
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
2017-09-07 15:19:06 +02:00
|
|
|
}
|
2018-04-05 19:42:27 +02:00
|
|
|
nexthop = bgp_info_to_ipv6_nexthop(mpinfo_cp,
|
|
|
|
&ifindex);
|
|
|
|
nh_updated = update_ipv6nh_for_route_install(
|
|
|
|
nh_othervrf, nexthop, ifindex,
|
|
|
|
mpinfo, info, is_evpn, api_nh);
|
2017-08-21 02:36:44 +02:00
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2018-04-05 19:42:27 +02:00
|
|
|
/* Did we get proper nexthop info to update zebra? */
|
|
|
|
if (!nh_updated)
|
|
|
|
continue;
|
|
|
|
|
2018-02-09 19:22:50 +01:00
|
|
|
if (mpinfo->extra
|
|
|
|
&& bgp_is_valid_label(&mpinfo->extra->label[0])
|
2017-11-07 10:52:23 +01:00
|
|
|
&& !CHECK_FLAG(api.flags, ZEBRA_FLAG_EVPN_ROUTE)) {
|
2017-08-21 02:36:44 +02:00
|
|
|
has_valid_label = 1;
|
2017-11-21 11:42:05 +01:00
|
|
|
label = label_pton(&mpinfo->extra->label[0]);
|
2017-08-21 02:19:25 +02:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
api_nh->label_num = 1;
|
|
|
|
api_nh->labels[0] = label;
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
2017-11-29 08:40:30 +01:00
|
|
|
memcpy(&api_nh->rmac, &(mpinfo->attr->rmac),
|
|
|
|
sizeof(struct ethaddr));
|
2017-08-21 02:36:44 +02:00
|
|
|
valid_nh_count++;
|
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2018-04-05 19:42:27 +02:00
|
|
|
|
2017-10-16 06:19:04 +02:00
|
|
|
/* if this is a evpn route we don't have to include the label */
|
2018-02-09 19:22:50 +01:00
|
|
|
if (has_valid_label && !(CHECK_FLAG(api.flags, ZEBRA_FLAG_EVPN_ROUTE)))
|
2017-08-21 02:36:44 +02:00
|
|
|
SET_FLAG(api.message, ZAPI_MESSAGE_LABEL);
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2018-05-30 02:04:17 +02:00
|
|
|
/*
|
|
|
|
* When we create an aggregate route we must also
|
|
|
|
* install a Null0 route in the RIB, so overwrite
|
|
|
|
* what was written into api with a blackhole route
|
|
|
|
*/
|
|
|
|
if (info->sub_type == BGP_ROUTE_AGGREGATE)
|
|
|
|
zapi_route_set_blackhole(&api, BLACKHOLE_NULL);
|
|
|
|
else
|
2017-08-21 02:36:44 +02:00
|
|
|
api.nexthop_num = valid_nh_count;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
SET_FLAG(api.message, ZAPI_MESSAGE_METRIC);
|
|
|
|
api.metric = metric;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
if (tag) {
|
|
|
|
SET_FLAG(api.message, ZAPI_MESSAGE_TAG);
|
|
|
|
api.tag = tag;
|
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
distance = bgp_distance_apply(p, info, afi, safi, bgp);
|
|
|
|
if (distance) {
|
|
|
|
SET_FLAG(api.message, ZAPI_MESSAGE_DISTANCE);
|
|
|
|
api.distance = distance;
|
|
|
|
}
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
if (bgp_debug_zebra(p)) {
|
|
|
|
char prefix_buf[PREFIX_STRLEN];
|
|
|
|
char nh_buf[INET6_ADDRSTRLEN];
|
|
|
|
char label_buf[20];
|
|
|
|
int i;
|
|
|
|
|
|
|
|
prefix2str(&api.prefix, prefix_buf, sizeof(prefix_buf));
|
|
|
|
zlog_debug("Tx route %s VRF %u %s metric %u tag %" ROUTE_TAG_PRI
|
|
|
|
" count %d",
|
|
|
|
valid_nh_count ? "add" : "delete", bgp->vrf_id,
|
|
|
|
prefix_buf, api.metric, api.tag, api.nexthop_num);
|
|
|
|
for (i = 0; i < api.nexthop_num; i++) {
|
|
|
|
api_nh = &api.nexthops[i];
|
|
|
|
|
2018-04-05 19:42:27 +02:00
|
|
|
if (api_nh->type == NEXTHOP_TYPE_IFINDEX)
|
|
|
|
nh_buf[0] = '\0';
|
|
|
|
else {
|
|
|
|
if (api_nh->type == NEXTHOP_TYPE_IPV4)
|
|
|
|
nh_family = AF_INET;
|
|
|
|
else
|
|
|
|
nh_family = AF_INET6;
|
|
|
|
inet_ntop(nh_family, &api_nh->gate, nh_buf,
|
|
|
|
sizeof(nh_buf));
|
|
|
|
}
|
2017-08-21 02:36:44 +02:00
|
|
|
|
|
|
|
label_buf[0] = '\0';
|
2018-02-09 19:22:50 +01:00
|
|
|
if (has_valid_label
|
|
|
|
&& !CHECK_FLAG(api.flags, ZEBRA_FLAG_EVPN_ROUTE))
|
2017-08-21 02:36:44 +02:00
|
|
|
sprintf(label_buf, "label %u",
|
|
|
|
api_nh->labels[0]);
|
2018-04-05 19:42:27 +02:00
|
|
|
zlog_debug(" nhop [%d]: %s if %u VRF %u %s",
|
|
|
|
i + 1, nh_buf, api_nh->ifindex,
|
|
|
|
api_nh->vrf_id, label_buf);
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
|
|
|
}
|
2017-08-21 02:36:44 +02:00
|
|
|
|
2018-03-24 00:57:03 +01:00
|
|
|
if (bgp_debug_zebra(p)) {
|
|
|
|
int recursion_flag = 0;
|
|
|
|
|
|
|
|
if (CHECK_FLAG(api.flags, ZEBRA_FLAG_ALLOW_RECURSION))
|
|
|
|
recursion_flag = 1;
|
|
|
|
|
|
|
|
zlog_debug("%s: %s: announcing to zebra (recursion %sset)",
|
|
|
|
__func__, buf_prefix,
|
|
|
|
(recursion_flag ? "" : "NOT "));
|
|
|
|
}
|
2017-08-21 02:36:44 +02:00
|
|
|
zclient_route_send(valid_nh_count ? ZEBRA_ROUTE_ADD
|
|
|
|
: ZEBRA_ROUTE_DELETE,
|
|
|
|
zclient, &api);
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
bgpd: bgpd-table-map.patch
COMMAND:
table-map <route-map-name>
DESCRIPTION:
This feature is used to apply a route-map on route updates from BGP to Zebra.
All the applicable match operations are allowed, such as match on prefix,
next-hop, communities, etc. Set operations for this attach-point are limited
to metric and next-hop only. Any operation of this feature does not affect
BGPs internal RIB.
Supported for ipv4 and ipv6 address families. It works on multi-paths as well,
however, metric setting is based on the best-path only.
IMPLEMENTATION NOTES:
The route-map application at this point is not supposed to modify any of BGP
route's attributes (anything in bgp_info for that matter). To achieve that,
creating a copy of the bgp_attr was inevitable. Implementation tries to keep
the memory footprint low, code comments do point out the rationale behind a
few choices made.
bgp_zebra_announce() was already a big routine, adding this feature would
extend it further. Patch has created a few smaller routines/macros whereever
possible to keep the size of the routine in check without compromising on the
readability of the code/flow inside this routine.
For updating a partially filtered route (with its nexthops), BGP to Zebra
replacement semantic of the next-hops serves the purpose well. However, with
this patch there could be some redundant withdraws each time BGP announces a
route thats (all the nexthops) gets denied by the route-map application.
Handling of this case could be optimized by keeping state with the prefix and
the nexthops in BGP. The patch doesn't optimizing that case, as even with the
redundant withdraws the total number of updates to zebra are still be capped
by the total number of routes in the table.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Pradosh Mohapatra <pmohapat@cumulusnetworks.com>
2015-05-20 02:40:34 +02:00
|
|
|
/* Announce all routes of a table to zebra */
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zebra_announce_table(struct bgp *bgp, afi_t afi, safi_t safi)
|
bgpd: bgpd-table-map.patch
COMMAND:
table-map <route-map-name>
DESCRIPTION:
This feature is used to apply a route-map on route updates from BGP to Zebra.
All the applicable match operations are allowed, such as match on prefix,
next-hop, communities, etc. Set operations for this attach-point are limited
to metric and next-hop only. Any operation of this feature does not affect
BGPs internal RIB.
Supported for ipv4 and ipv6 address families. It works on multi-paths as well,
however, metric setting is based on the best-path only.
IMPLEMENTATION NOTES:
The route-map application at this point is not supposed to modify any of BGP
route's attributes (anything in bgp_info for that matter). To achieve that,
creating a copy of the bgp_attr was inevitable. Implementation tries to keep
the memory footprint low, code comments do point out the rationale behind a
few choices made.
bgp_zebra_announce() was already a big routine, adding this feature would
extend it further. Patch has created a few smaller routines/macros whereever
possible to keep the size of the routine in check without compromising on the
readability of the code/flow inside this routine.
For updating a partially filtered route (with its nexthops), BGP to Zebra
replacement semantic of the next-hops serves the purpose well. However, with
this patch there could be some redundant withdraws each time BGP announces a
route thats (all the nexthops) gets denied by the route-map application.
Handling of this case could be optimized by keeping state with the prefix and
the nexthops in BGP. The patch doesn't optimizing that case, as even with the
redundant withdraws the total number of updates to zebra are still be capped
by the total number of routes in the table.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Pradosh Mohapatra <pmohapat@cumulusnetworks.com>
2015-05-20 02:40:34 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct bgp_node *rn;
|
|
|
|
struct bgp_table *table;
|
|
|
|
struct bgp_info *ri;
|
|
|
|
|
|
|
|
/* Don't try to install if we're not connected to Zebra or Zebra doesn't
|
|
|
|
* know of this instance.
|
|
|
|
*/
|
|
|
|
if (!bgp_install_info_to_zebra(bgp))
|
|
|
|
return;
|
|
|
|
|
|
|
|
table = bgp->rib[afi][safi];
|
|
|
|
if (!table)
|
|
|
|
return;
|
|
|
|
|
|
|
|
for (rn = bgp_table_top(table); rn; rn = bgp_route_next(rn))
|
|
|
|
for (ri = rn->info; ri; ri = ri->next)
|
2018-03-09 21:52:55 +01:00
|
|
|
if (CHECK_FLAG(ri->flags, BGP_INFO_SELECTED) &&
|
|
|
|
|
|
|
|
(ri->type == ZEBRA_ROUTE_BGP
|
|
|
|
&& (ri->sub_type == BGP_ROUTE_NORMAL
|
|
|
|
|| ri->sub_type == BGP_ROUTE_IMPORTED)))
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_zebra_announce(rn, &rn->p, ri, bgp, afi,
|
|
|
|
safi);
|
bgpd: bgpd-table-map.patch
COMMAND:
table-map <route-map-name>
DESCRIPTION:
This feature is used to apply a route-map on route updates from BGP to Zebra.
All the applicable match operations are allowed, such as match on prefix,
next-hop, communities, etc. Set operations for this attach-point are limited
to metric and next-hop only. Any operation of this feature does not affect
BGPs internal RIB.
Supported for ipv4 and ipv6 address families. It works on multi-paths as well,
however, metric setting is based on the best-path only.
IMPLEMENTATION NOTES:
The route-map application at this point is not supposed to modify any of BGP
route's attributes (anything in bgp_info for that matter). To achieve that,
creating a copy of the bgp_attr was inevitable. Implementation tries to keep
the memory footprint low, code comments do point out the rationale behind a
few choices made.
bgp_zebra_announce() was already a big routine, adding this feature would
extend it further. Patch has created a few smaller routines/macros whereever
possible to keep the size of the routine in check without compromising on the
readability of the code/flow inside this routine.
For updating a partially filtered route (with its nexthops), BGP to Zebra
replacement semantic of the next-hops serves the purpose well. However, with
this patch there could be some redundant withdraws each time BGP announces a
route thats (all the nexthops) gets denied by the route-map application.
Handling of this case could be optimized by keeping state with the prefix and
the nexthops in BGP. The patch doesn't optimizing that case, as even with the
redundant withdraws the total number of updates to zebra are still be capped
by the total number of routes in the table.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Pradosh Mohapatra <pmohapat@cumulusnetworks.com>
2015-05-20 02:40:34 +02:00
|
|
|
}
|
|
|
|
|
2017-11-01 21:36:46 +01:00
|
|
|
void bgp_zebra_withdraw(struct prefix *p, struct bgp_info *info,
|
|
|
|
struct bgp *bgp, safi_t safi)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-08-21 02:36:44 +02:00
|
|
|
struct zapi_route api;
|
2018-03-28 14:51:57 +02:00
|
|
|
struct peer *peer;
|
2018-03-09 21:52:55 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Don't try to install if we're not connected to Zebra or Zebra doesn't
|
|
|
|
* know of this instance.
|
|
|
|
*/
|
2017-11-01 21:36:46 +01:00
|
|
|
if (!bgp_install_info_to_zebra(bgp))
|
2017-07-17 14:03:14 +02:00
|
|
|
return;
|
|
|
|
|
2018-03-28 14:51:57 +02:00
|
|
|
if (safi == SAFI_FLOWSPEC) {
|
|
|
|
peer = info->peer;
|
2018-01-26 18:36:24 +01:00
|
|
|
return bgp_pbr_update_entry(peer->bgp, p,
|
|
|
|
info, AFI_IP, safi, false);
|
2018-03-28 14:51:57 +02:00
|
|
|
}
|
2018-01-26 18:36:24 +01:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
memset(&api, 0, sizeof(api));
|
2017-11-01 21:36:46 +01:00
|
|
|
api.vrf_id = bgp->vrf_id;
|
2017-08-21 02:36:44 +02:00
|
|
|
api.type = ZEBRA_ROUTE_BGP;
|
|
|
|
api.safi = safi;
|
|
|
|
api.prefix = *p;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2018-03-30 02:24:00 +02:00
|
|
|
/* If the route's source is EVPN, flag as such. */
|
|
|
|
if (is_route_parent_evpn(info))
|
2017-11-07 10:52:23 +01:00
|
|
|
SET_FLAG(api.flags, ZEBRA_FLAG_EVPN_ROUTE);
|
2017-10-17 02:31:36 +02:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
if (bgp_debug_zebra(p)) {
|
|
|
|
char buf[PREFIX_STRLEN];
|
2017-07-17 14:03:14 +02:00
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
prefix2str(&api.prefix, buf, sizeof(buf));
|
2017-11-01 21:36:46 +01:00
|
|
|
zlog_debug("Tx route delete VRF %u %s", bgp->vrf_id, buf);
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
|
|
|
|
2017-08-21 02:36:44 +02:00
|
|
|
zclient_route_send(ZEBRA_ROUTE_DELETE, zclient, &api);
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2017-01-13 13:57:57 +01:00
|
|
|
|
2018-03-27 21:13:34 +02:00
|
|
|
struct bgp_redist *bgp_redist_lookup(struct bgp *bgp, afi_t afi, uint8_t type,
|
|
|
|
unsigned short instance)
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct list *red_list;
|
|
|
|
struct listnode *node;
|
|
|
|
struct bgp_redist *red;
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
red_list = bgp->redist[afi][type];
|
|
|
|
if (!red_list)
|
|
|
|
return (NULL);
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
for (ALL_LIST_ELEMENTS_RO(red_list, node, red))
|
|
|
|
if (red->instance == instance)
|
|
|
|
return red;
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return NULL;
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
}
|
|
|
|
|
2018-03-27 21:13:34 +02:00
|
|
|
struct bgp_redist *bgp_redist_add(struct bgp *bgp, afi_t afi, uint8_t type,
|
|
|
|
unsigned short instance)
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct list *red_list;
|
|
|
|
struct bgp_redist *red;
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
red = bgp_redist_lookup(bgp, afi, type, instance);
|
|
|
|
if (red)
|
|
|
|
return red;
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (!bgp->redist[afi][type])
|
|
|
|
bgp->redist[afi][type] = list_new();
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
red_list = bgp->redist[afi][type];
|
|
|
|
red = (struct bgp_redist *)XCALLOC(MTYPE_BGP_REDIST,
|
|
|
|
sizeof(struct bgp_redist));
|
|
|
|
red->instance = instance;
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
listnode_add(red_list, red);
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return red;
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
}
|
|
|
|
|
2018-03-27 21:13:34 +02:00
|
|
|
static void bgp_redist_del(struct bgp *bgp, afi_t afi, uint8_t type,
|
|
|
|
unsigned short instance)
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct bgp_redist *red;
|
|
|
|
|
|
|
|
red = bgp_redist_lookup(bgp, afi, type, instance);
|
|
|
|
|
|
|
|
if (red) {
|
|
|
|
listnode_delete(bgp->redist[afi][type], red);
|
|
|
|
XFREE(MTYPE_BGP_REDIST, red);
|
2017-09-28 03:19:20 +02:00
|
|
|
if (!bgp->redist[afi][type]->count)
|
|
|
|
list_delete_and_null(&bgp->redist[afi][type]);
|
2017-07-17 14:03:14 +02:00
|
|
|
}
|
Multi-Instance OSPF Summary
——————————————-------------
- etc/init.d/quagga is modified to support creating separate ospf daemon
process for each instance. Each individual instance is monitored by
watchquagga just like any protocol daemons.(requires initd-mi.patch).
- Vtysh is modified to able to connect to multiple daemons of the same
protocol (supported for OSPF only for now).
- ospfd is modified to remember the Instance-ID that its invoked with. For
the entire life of the process it caters to any command request that
matches that instance-ID (unless its a non instance specific command).
Routes/messages to zebra are tagged with instance-ID.
- zebra route/redistribute mechanisms are modified to work with
[protocol type + instance-id]
- bgpd now has ability to have multiple instance specific redistribution
for a protocol (OSPF only supported/tested for now).
- zlog ability to display instance-id besides the protocol/daemon name.
- Changes in other daemons are to because of the needed integration with
some of the modified APIs/routines. (Didn’t prefer replicating too many
separate instance specific APIs.)
- config/show/debug commands are modified to take instance-id argument
as appropriate.
Guidelines to start using multi-instance ospf
---------------------------------------------
The patch is backward compatible, i.e for any previous way of single ospf
deamon(router ospf <cr>) will continue to work as is, including all the
show commands etc.
To enable multiple instances, do the following:
1. service quagga stop
2. Modify /etc/quagga/daemons to add instance-ids of each desired
instance in the following format:
ospfd=“yes"
ospfd_instances="1,2,3"
assuming you want to enable 3 instances with those instance ids.
3. Create corresponding ospfd config files as ospfd-1.conf, ospfd-2.conf
and ospfd-3.conf.
4. service quagga start/restart
5. Verify that the deamons are started as expected. You should see
ospfd started with -n <instance-id> option.
ps –ef | grep quagga
With that /var/run/quagga/ should have ospfd-<instance-id>.pid and
ospfd-<instance-id>/vty to each instance.
6. vtysh to work with instances as you would with any other deamons.
7. Overall most quagga semantics are the same working with the instance
deamon, like it is for any other daemon.
NOTE:
To safeguard against errors leading to too many processes getting invoked,
a hard limit on number of instance-ids is in place, currently its 5.
Allowed instance-id range is <1-65535>
Once daemons are up, show running from vtysh should show the instance-id
of each daemon as 'router ospf <instance-id>’ (without needing explicit
configuration)
Instance-id can not be changed via vtysh, other router ospf configuration
is allowed as before.
Signed-off-by: Vipin Kumar <vipin@cumulusnetworks.com>
Reviewed-by: Daniel Walton <dwalton@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
2015-05-20 03:03:42 +02:00
|
|
|
}
|
2014-06-04 06:53:35 +02:00
|
|
|
|
2002-12-13 21:15:29 +01:00
|
|
|
/* Other routes redistribution into BGP. */
|
2018-03-27 21:13:34 +02:00
|
|
|
int bgp_redistribute_set(struct bgp *bgp, afi_t afi, int type,
|
|
|
|
unsigned short instance)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Return if already redistribute flag is set. */
|
|
|
|
if (instance) {
|
|
|
|
if (redist_check_instance(&zclient->mi_redist[afi][type],
|
|
|
|
instance))
|
|
|
|
return CMD_WARNING;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
redist_add_instance(&zclient->mi_redist[afi][type], instance);
|
|
|
|
} else {
|
|
|
|
if (vrf_bitmap_check(zclient->redist[afi][type], bgp->vrf_id))
|
|
|
|
return CMD_WARNING;
|
*: add VRF ID in the API message header
The API messages are used by zebra to exchange the interfaces, addresses,
routes and router-id information with its clients. To distinguish which
VRF the information belongs to, a new field "VRF ID" is added in the
message header. And hence the message version is increased to 3.
* The new field "VRF ID" in the message header:
Length (2 bytes)
Marker (1 byte)
Version (1 byte)
VRF ID (2 bytes, newly added)
Command (2 bytes)
- Client side:
- zclient_create_header() adds the VRF ID in the message header.
- zclient_read() extracts and validates the VRF ID from the header,
and passes the VRF ID to the callback functions registered to
the API messages.
- All relative functions are appended with a new parameter "vrf_id",
including all the callback functions.
- "vrf_id" is also added to "struct zapi_ipv4" and "struct zapi_ipv6".
Clients need to correctly set the VRF ID when using the API
functions zapi_ipv4_route() and zapi_ipv6_route().
- Till now all messages sent from a client have the default VRF ID
"0" in the header.
- The HELLO message is special, which is used as the heart-beat of
a client, and has no relation with VRF. The VRF ID in the HELLO
message header will always be 0 and ignored by zebra.
- Zebra side:
- zserv_create_header() adds the VRF ID in the message header.
- zebra_client_read() extracts and validates the VRF ID from the
header, and passes the VRF ID to the functions which process
the received messages.
- All relative functions are appended with a new parameter "vrf_id".
* Suppress the messages in a VRF which a client does not care:
Some clients may not care about the information in the VRF X, and
zebra should not send the messages in the VRF X to those clients.
Extra flags are used to indicate which VRF is registered by a client,
and a new message ZEBRA_VRF_UNREGISTER is introduced to let a client
can unregister a VRF when it does not need any information in that
VRF.
A client sends any message other than ZEBRA_VRF_UNREGISTER in a VRF
will automatically register to that VRF.
- lib/vrf:
A new utility "VRF bit-map" is provided to manage the flags for
VRFs, one bit per VRF ID.
- Use vrf_bitmap_init()/vrf_bitmap_free() to initialize/free a
bit-map;
- Use vrf_bitmap_set()/vrf_bitmap_unset() to set/unset a flag
in the given bit-map, corresponding to the given VRF ID;
- Use vrf_bitmap_check() to test whether the flag, in the given
bit-map and for the given VRF ID, is set.
- Client side:
- In "struct zclient", the following flags are changed from
"u_char" to "vrf_bitmap_t":
redist[ZEBRA_ROUTE_MAX]
default_information
These flags are extended for each VRF, and controlled by the
clients themselves (or with the help of zclient_redistribute()
and zclient_redistribute_default()).
- Zebra side:
- In "struct zserv", the following flags are changed from
"u_char" to "vrf_bitmap_t":
redist[ZEBRA_ROUTE_MAX]
redist_default
ifinfo
ridinfo
These flags are extended for each VRF, as the VRF registration
flags. They are maintained on receiving a ZEBRA_XXX_ADD or
ZEBRA_XXX_DELETE message.
When sending an interface/address/route/router-id message in
a VRF to a client, if the corresponding VRF registration flag
is not set, this message will not be dropped by zebra.
- A new function zread_vrf_unregister() is introduced to process
the new command ZEBRA_VRF_UNREGISTER. All the VRF registration
flags are cleared for the requested VRF.
Those clients, who support only the default VRF, will never receive
a message in a non-default VRF, thanks to the filter in zebra.
* New callback for the event of successful connection to zebra:
- zclient_start() is splitted, keeping only the code of connecting
to zebra.
- Now zclient_init()=>zclient_connect()=>zclient_start() operations
are purely dealing with the connection to zbera.
- Once zebra is successfully connected, at the end of zclient_start(),
a new callback is used to inform the client about connection.
- Till now, in the callback of connect-to-zebra event, all clients
send messages to zebra to request the router-id/interface/routes
information in the default VRF.
Of corse in future the client can do anything it wants in this
callback. For example, it may send requests for both default VRF
and some non-default VRFs.
Signed-off-by: Feng Lu <lu.feng@6wind.com>
Reviewed-by: Alain Ritoux <alain.ritoux@6wind.com>
Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Acked-by: Donald Sharp <sharpd@cumulusnetworks.com>
Conflicts:
lib/zclient.h
lib/zebra.h
zebra/zserv.c
zebra/zserv.h
Conflicts:
bgpd/bgp_nexthop.c
bgpd/bgp_nht.c
bgpd/bgp_zebra.c
isisd/isis_zebra.c
lib/zclient.c
lib/zclient.h
lib/zebra.h
nhrpd/nhrp_interface.c
nhrpd/nhrp_route.c
nhrpd/nhrpd.h
ospf6d/ospf6_zebra.c
ospf6d/ospf6_zebra.h
ospfd/ospf_vty.c
ospfd/ospf_zebra.c
pimd/pim_zebra.c
pimd/pim_zlookup.c
ripd/rip_zebra.c
ripngd/ripng_zebra.c
zebra/redistribute.c
zebra/rt_netlink.c
zebra/zebra_rnh.c
zebra/zebra_rnh.h
zebra/zserv.c
zebra/zserv.h
2014-10-16 03:52:36 +02:00
|
|
|
|
bgpd: add L3/L2VPN Virtual Network Control feature
This feature adds an L3 & L2 VPN application that makes use of the VPN
and Encap SAFIs. This code is currently used to support IETF NVO3 style
operation. In NVO3 terminology it provides the Network Virtualization
Authority (NVA) and the ability to import/export IP prefixes and MAC
addresses from Network Virtualization Edges (NVEs). The code supports
per-NVE tables.
The NVE-NVA protocol used to communicate routing and Ethernet / Layer 2
(L2) forwarding information between NVAs and NVEs is referred to as the
Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. For
general background on NVO3 and RFP concepts see [1]. For information on
Openflow see [2].
RFPs are integrated with BGP via the RF API contained in the new "rfapi"
BGP sub-directory. Currently, only a simple example RFP is included in
Quagga. Developers may use this example as a starting point to integrate
Quagga with an RFP of their choosing, e.g., OpenFlow. The RFAPI code
also supports the ability import/export of routing information between
VNC and customer edge routers (CEs) operating within a virtual
network. Import/export may take place between BGP views or to the
default zebera VRF.
BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VPN
information between NVAs. BGP based IP VPN support is defined in
RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659,
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Use
of both the Encapsulation Subsequent Address Family Identifier (SAFI)
and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute, are supported. MAC address distribution does
not follow any standard BGB encoding, although it was inspired by the
early IETF EVPN concepts.
The feature is conditionally compiled and disabled by default.
Use the --enable-bgp-vnc configure option to enable.
The majority of this code was authored by G. Paul Ziemba
<paulz@labn.net>.
[1] http://tools.ietf.org/html/draft-ietf-nvo3-nve-nva-cp-req
[2] https://www.opennetworking.org/sdn-resources/technical-library
Now includes changes needed to merge with cmaster-next.
2016-05-07 20:18:56 +02:00
|
|
|
#if ENABLE_BGP_VNC
|
2017-07-17 14:03:14 +02:00
|
|
|
if (bgp->vrf_id == VRF_DEFAULT
|
|
|
|
&& type == ZEBRA_ROUTE_VNC_DIRECT) {
|
|
|
|
vnc_export_bgp_enable(
|
|
|
|
bgp, afi); /* only enables if mode bits cfg'd */
|
|
|
|
}
|
bgpd: add L3/L2VPN Virtual Network Control feature
This feature adds an L3 & L2 VPN application that makes use of the VPN
and Encap SAFIs. This code is currently used to support IETF NVO3 style
operation. In NVO3 terminology it provides the Network Virtualization
Authority (NVA) and the ability to import/export IP prefixes and MAC
addresses from Network Virtualization Edges (NVEs). The code supports
per-NVE tables.
The NVE-NVA protocol used to communicate routing and Ethernet / Layer 2
(L2) forwarding information between NVAs and NVEs is referred to as the
Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. For
general background on NVO3 and RFP concepts see [1]. For information on
Openflow see [2].
RFPs are integrated with BGP via the RF API contained in the new "rfapi"
BGP sub-directory. Currently, only a simple example RFP is included in
Quagga. Developers may use this example as a starting point to integrate
Quagga with an RFP of their choosing, e.g., OpenFlow. The RFAPI code
also supports the ability import/export of routing information between
VNC and customer edge routers (CEs) operating within a virtual
network. Import/export may take place between BGP views or to the
default zebera VRF.
BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VPN
information between NVAs. BGP based IP VPN support is defined in
RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659,
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Use
of both the Encapsulation Subsequent Address Family Identifier (SAFI)
and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute, are supported. MAC address distribution does
not follow any standard BGB encoding, although it was inspired by the
early IETF EVPN concepts.
The feature is conditionally compiled and disabled by default.
Use the --enable-bgp-vnc configure option to enable.
The majority of this code was authored by G. Paul Ziemba
<paulz@labn.net>.
[1] http://tools.ietf.org/html/draft-ietf-nvo3-nve-nva-cp-req
[2] https://www.opennetworking.org/sdn-resources/technical-library
Now includes changes needed to merge with cmaster-next.
2016-05-07 20:18:56 +02:00
|
|
|
#endif
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
vrf_bitmap_set(zclient->redist[afi][type], bgp->vrf_id);
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-10-26 04:38:50 +02:00
|
|
|
/*
|
|
|
|
* Don't try to register if we're not connected to Zebra or Zebra
|
|
|
|
* doesn't know of this instance.
|
|
|
|
*
|
|
|
|
* When we come up later well resend if needed.
|
2017-07-17 14:03:14 +02:00
|
|
|
*/
|
|
|
|
if (!bgp_install_info_to_zebra(bgp))
|
2017-10-26 04:38:50 +02:00
|
|
|
return CMD_SUCCESS;
|
[bgpd] Implement 'debug bgp zebra' to log all messages to and from zebra.
2006-11-30 Andrew J. Schorr <ajschorr@alumni.princeton.edu>
* bgp_debug.h: Declare new bgp_debug_zebra conf and term flags,
and define BGP_DEBUG_ZEBRA.
* bgp_debug.c: Declare conf_bgp_debug_zebra and term_bgp_debug_zebra.
(debug_bgp_zebra, no_debug_bgp_zebra, undebug_bgp_zebra) New
functions to enable/disable bgp zebra debugging.
(no_debug_bgp_all) Turn off zebra debugging.
(show_debugging_bgp) Show whether zebra debugging is on.
(bgp_config_write_debug) Add 'debug bgp zebra' if configured.
(bgp_debug_init) Add new zebra debugging commands.
* bgp_zebra.c: (bgp_router_id_update, bgp_interface_add,
bgp_interface_delete, bgp_interface_up, bgp_interface_down,
bgp_interface_address_add, bgp_interface_address_delete,
zebra_read_ipv4, zebra_read_ipv6, bgp_zebra_announce,
bgp_zebra_withdraw, bgp_redistribute_set, bgp_redistribute_unset)
If zebra debugging is enabled, log an appropriate debug message.
2006-11-30 17:36:57 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Tx redistribute add VRF %u afi %d %s %d",
|
|
|
|
bgp->vrf_id, afi, zebra_route_string(type),
|
|
|
|
instance);
|
2015-05-20 02:40:45 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Send distribute add message to zebra. */
|
|
|
|
zebra_redistribute_send(ZEBRA_REDISTRIBUTE_ADD, zclient, afi, type,
|
|
|
|
instance, bgp->vrf_id);
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return CMD_SUCCESS;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
int bgp_redistribute_resend(struct bgp *bgp, afi_t afi, int type,
|
2018-03-27 21:13:34 +02:00
|
|
|
unsigned short instance)
|
2015-05-20 02:40:45 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Don't try to send if we're not connected to Zebra or Zebra doesn't
|
|
|
|
* know of this instance.
|
|
|
|
*/
|
|
|
|
if (!bgp_install_info_to_zebra(bgp))
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Tx redistribute del/add VRF %u afi %d %s %d",
|
|
|
|
bgp->vrf_id, afi, zebra_route_string(type),
|
|
|
|
instance);
|
|
|
|
|
|
|
|
/* Send distribute add message to zebra. */
|
|
|
|
zebra_redistribute_send(ZEBRA_REDISTRIBUTE_DELETE, zclient, afi, type,
|
|
|
|
instance, bgp->vrf_id);
|
|
|
|
zebra_redistribute_send(ZEBRA_REDISTRIBUTE_ADD, zclient, afi, type,
|
|
|
|
instance, bgp->vrf_id);
|
|
|
|
|
|
|
|
return 0;
|
2015-05-20 02:40:45 +02:00
|
|
|
}
|
|
|
|
|
2002-12-13 21:15:29 +01:00
|
|
|
/* Redistribute with route-map specification. */
|
2017-07-17 14:03:14 +02:00
|
|
|
int bgp_redistribute_rmap_set(struct bgp_redist *red, const char *name)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
if (red->rmap.name && (strcmp(red->rmap.name, name) == 0))
|
|
|
|
return 0;
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (red->rmap.name)
|
|
|
|
XFREE(MTYPE_ROUTE_MAP_NAME, red->rmap.name);
|
|
|
|
red->rmap.name = XSTRDUP(MTYPE_ROUTE_MAP_NAME, name);
|
|
|
|
red->rmap.map = route_map_lookup_by_name(name);
|
2002-12-13 21:15:29 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return 1;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Redistribute with metric specification. */
|
2017-07-17 14:03:14 +02:00
|
|
|
int bgp_redistribute_metric_set(struct bgp *bgp, struct bgp_redist *red,
|
2018-03-27 21:13:34 +02:00
|
|
|
afi_t afi, int type, uint32_t metric)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct bgp_node *rn;
|
|
|
|
struct bgp_info *ri;
|
|
|
|
|
|
|
|
if (red->redist_metric_flag && red->redist_metric == metric)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
red->redist_metric_flag = 1;
|
|
|
|
red->redist_metric = metric;
|
|
|
|
|
|
|
|
for (rn = bgp_table_top(bgp->rib[afi][SAFI_UNICAST]); rn;
|
|
|
|
rn = bgp_route_next(rn)) {
|
|
|
|
for (ri = rn->info; ri; ri = ri->next) {
|
|
|
|
if (ri->sub_type == BGP_ROUTE_REDISTRIBUTE
|
|
|
|
&& ri->type == type
|
|
|
|
&& ri->instance == red->instance) {
|
|
|
|
struct attr *old_attr;
|
|
|
|
struct attr new_attr;
|
|
|
|
|
|
|
|
bgp_attr_dup(&new_attr, ri->attr);
|
|
|
|
new_attr.med = red->redist_metric;
|
|
|
|
old_attr = ri->attr;
|
|
|
|
ri->attr = bgp_attr_intern(&new_attr);
|
|
|
|
bgp_attr_unintern(&old_attr);
|
|
|
|
|
|
|
|
bgp_info_set_flag(rn, ri,
|
|
|
|
BGP_INFO_ATTR_CHANGED);
|
|
|
|
bgp_process(bgp, rn, afi, SAFI_UNICAST);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return 1;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Unset redistribution. */
|
2017-07-17 14:03:14 +02:00
|
|
|
int bgp_redistribute_unreg(struct bgp *bgp, afi_t afi, int type,
|
2018-03-27 21:13:34 +02:00
|
|
|
unsigned short instance)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct bgp_redist *red;
|
|
|
|
|
|
|
|
red = bgp_redist_lookup(bgp, afi, type, instance);
|
|
|
|
if (!red)
|
|
|
|
return CMD_SUCCESS;
|
|
|
|
|
|
|
|
/* Return if zebra connection is disabled. */
|
|
|
|
if (instance) {
|
|
|
|
if (!redist_check_instance(&zclient->mi_redist[afi][type],
|
|
|
|
instance))
|
|
|
|
return CMD_WARNING;
|
|
|
|
redist_del_instance(&zclient->mi_redist[afi][type], instance);
|
|
|
|
} else {
|
|
|
|
if (!vrf_bitmap_check(zclient->redist[afi][type], bgp->vrf_id))
|
|
|
|
return CMD_WARNING;
|
|
|
|
vrf_bitmap_unset(zclient->redist[afi][type], bgp->vrf_id);
|
|
|
|
}
|
2002-12-13 21:15:29 +01:00
|
|
|
|
bgpd: add L3/L2VPN Virtual Network Control feature
This feature adds an L3 & L2 VPN application that makes use of the VPN
and Encap SAFIs. This code is currently used to support IETF NVO3 style
operation. In NVO3 terminology it provides the Network Virtualization
Authority (NVA) and the ability to import/export IP prefixes and MAC
addresses from Network Virtualization Edges (NVEs). The code supports
per-NVE tables.
The NVE-NVA protocol used to communicate routing and Ethernet / Layer 2
(L2) forwarding information between NVAs and NVEs is referred to as the
Remote Forwarder Protocol (RFP). OpenFlow is an example RFP. For
general background on NVO3 and RFP concepts see [1]. For information on
Openflow see [2].
RFPs are integrated with BGP via the RF API contained in the new "rfapi"
BGP sub-directory. Currently, only a simple example RFP is included in
Quagga. Developers may use this example as a starting point to integrate
Quagga with an RFP of their choosing, e.g., OpenFlow. The RFAPI code
also supports the ability import/export of routing information between
VNC and customer edge routers (CEs) operating within a virtual
network. Import/export may take place between BGP views or to the
default zebera VRF.
BGP, with IP VPNs and Tunnel Encapsulation, is used to distribute VPN
information between NVAs. BGP based IP VPN support is defined in
RFC4364, BGP/MPLS IP Virtual Private Networks (VPNs), and RFC4659,
BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN . Use
of both the Encapsulation Subsequent Address Family Identifier (SAFI)
and the Tunnel Encapsulation Attribute, RFC5512, The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP Tunnel
Encapsulation Attribute, are supported. MAC address distribution does
not follow any standard BGB encoding, although it was inspired by the
early IETF EVPN concepts.
The feature is conditionally compiled and disabled by default.
Use the --enable-bgp-vnc configure option to enable.
The majority of this code was authored by G. Paul Ziemba
<paulz@labn.net>.
[1] http://tools.ietf.org/html/draft-ietf-nvo3-nve-nva-cp-req
[2] https://www.opennetworking.org/sdn-resources/technical-library
Now includes changes needed to merge with cmaster-next.
2016-05-07 20:18:56 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (bgp_install_info_to_zebra(bgp)) {
|
|
|
|
/* Send distribute delete message to zebra. */
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Tx redistribute del VRF %u afi %d %s %d",
|
|
|
|
bgp->vrf_id, afi, zebra_route_string(type),
|
|
|
|
instance);
|
|
|
|
zebra_redistribute_send(ZEBRA_REDISTRIBUTE_DELETE, zclient, afi,
|
|
|
|
type, instance, bgp->vrf_id);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Withdraw redistributed routes from current BGP's routing table. */
|
|
|
|
bgp_redistribute_withdraw(bgp, afi, type, instance);
|
|
|
|
|
|
|
|
return CMD_SUCCESS;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2016-02-02 13:36:20 +01:00
|
|
|
/* Unset redistribution. */
|
2017-07-17 14:03:14 +02:00
|
|
|
int bgp_redistribute_unset(struct bgp *bgp, afi_t afi, int type,
|
2018-03-27 21:13:34 +02:00
|
|
|
unsigned short instance)
|
2016-02-02 13:36:20 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct bgp_redist *red;
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2018-03-09 21:52:55 +01:00
|
|
|
/*
|
|
|
|
* vnc and vpn->vrf checks must be before red check because
|
|
|
|
* they operate within bgpd irrespective of zebra connection
|
|
|
|
* status. red lookup fails if there is no zebra connection.
|
|
|
|
*/
|
|
|
|
#if ENABLE_BGP_VNC
|
|
|
|
if (bgp->vrf_id == VRF_DEFAULT && type == ZEBRA_ROUTE_VNC_DIRECT) {
|
|
|
|
vnc_export_bgp_disable(bgp, afi);
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
red = bgp_redist_lookup(bgp, afi, type, instance);
|
|
|
|
if (!red)
|
|
|
|
return CMD_SUCCESS;
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_redistribute_unreg(bgp, afi, type, instance);
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Unset route-map. */
|
|
|
|
if (red->rmap.name)
|
|
|
|
XFREE(MTYPE_ROUTE_MAP_NAME, red->rmap.name);
|
|
|
|
red->rmap.name = NULL;
|
|
|
|
red->rmap.map = NULL;
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Unset metric. */
|
|
|
|
red->redist_metric_flag = 0;
|
|
|
|
red->redist_metric = 0;
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_redist_del(bgp, afi, type, instance);
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return CMD_SUCCESS;
|
2016-02-02 13:36:20 +01:00
|
|
|
}
|
|
|
|
|
2016-08-06 01:49:39 +02:00
|
|
|
/* Update redistribute vrf bitmap during triggers like
|
|
|
|
restart networking or delete/add VRFs */
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_update_redist_vrf_bitmaps(struct bgp *bgp, vrf_id_t old_vrf_id)
|
2016-08-06 01:49:39 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
int i;
|
|
|
|
afi_t afi;
|
|
|
|
|
|
|
|
for (afi = AFI_IP; afi < AFI_MAX; afi++)
|
|
|
|
for (i = 0; i < ZEBRA_ROUTE_MAX; i++)
|
2018-01-10 20:40:45 +01:00
|
|
|
if ((old_vrf_id == VRF_UNKNOWN)
|
|
|
|
|| vrf_bitmap_check(zclient->redist[afi][i],
|
|
|
|
old_vrf_id)) {
|
2017-07-17 14:03:14 +02:00
|
|
|
vrf_bitmap_unset(zclient->redist[afi][i],
|
|
|
|
old_vrf_id);
|
|
|
|
vrf_bitmap_set(zclient->redist[afi][i],
|
|
|
|
bgp->vrf_id);
|
|
|
|
}
|
|
|
|
return;
|
2016-08-06 01:49:39 +02:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zclient_reset(void)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
zclient_reset(zclient);
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
|
|
|
|
2016-02-12 21:18:28 +01:00
|
|
|
/* Register this instance with Zebra. Invoked upon connect (for
|
|
|
|
* default instance) and when other VRFs are learnt (or created and
|
|
|
|
* already learnt).
|
|
|
|
*/
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zebra_instance_register(struct bgp *bgp)
|
2016-02-12 21:18:28 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Don't try to register if we're not connected to Zebra */
|
|
|
|
if (!zclient || zclient->sock < 0)
|
|
|
|
return;
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Registering VRF %u", bgp->vrf_id);
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Register for router-id, interfaces, redistributed routes. */
|
|
|
|
zclient_send_reg_requests(zclient, bgp->vrf_id);
|
2017-05-15 23:30:19 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* For default instance, register to learn about VNIs, if appropriate.
|
|
|
|
*/
|
2018-02-09 19:22:50 +01:00
|
|
|
if (bgp->inst_type == BGP_INSTANCE_TYPE_DEFAULT && is_evpn_enabled())
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_zebra_advertise_all_vni(bgp, 1);
|
2016-02-12 21:18:28 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Deregister this instance with Zebra. Invoked upon the instance
|
|
|
|
* being deleted (default or VRF) and it is already registered.
|
|
|
|
*/
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zebra_instance_deregister(struct bgp *bgp)
|
2016-02-12 21:18:28 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Don't try to deregister if we're not connected to Zebra */
|
|
|
|
if (zclient->sock < 0)
|
|
|
|
return;
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Deregistering VRF %u", bgp->vrf_id);
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* For default instance, unregister learning about VNIs, if appropriate.
|
|
|
|
*/
|
2018-02-09 19:22:50 +01:00
|
|
|
if (bgp->inst_type == BGP_INSTANCE_TYPE_DEFAULT && is_evpn_enabled())
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_zebra_advertise_all_vni(bgp, 0);
|
2017-05-15 23:30:19 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Deregister for router-id, interfaces, redistributed routes. */
|
|
|
|
zclient_send_dereg_requests(zclient, bgp->vrf_id);
|
2016-02-12 21:18:28 +01:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zebra_initiate_radv(struct bgp *bgp, struct peer *peer)
|
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
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
int ra_interval = BGP_UNNUM_DEFAULT_RA_INTERVAL;
|
2016-05-13 01:51:43 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Don't try to initiate if we're not connected to Zebra */
|
|
|
|
if (zclient->sock < 0)
|
|
|
|
return;
|
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
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%u: Initiating RA for peer %s", bgp->vrf_id,
|
|
|
|
peer->host);
|
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
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
zclient_send_interface_radv_req(zclient, bgp->vrf_id, peer->ifp, 1,
|
|
|
|
ra_interval);
|
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
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zebra_terminate_radv(struct bgp *bgp, struct peer *peer)
|
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
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Don't try to terminate if we're not connected to Zebra */
|
|
|
|
if (zclient->sock < 0)
|
|
|
|
return;
|
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
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%u: Terminating RA for peer %s", bgp->vrf_id,
|
|
|
|
peer->host);
|
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
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
zclient_send_interface_radv_req(zclient, bgp->vrf_id, peer->ifp, 0, 0);
|
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
|
|
|
}
|
|
|
|
|
2017-11-20 06:47:04 +01:00
|
|
|
int bgp_zebra_advertise_subnet(struct bgp *bgp, int advertise, vni_t vni)
|
|
|
|
{
|
|
|
|
struct stream *s = NULL;
|
|
|
|
|
|
|
|
/* Check socket. */
|
|
|
|
if (!zclient || zclient->sock < 0)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* Don't try to register if Zebra doesn't know of this instance. */
|
|
|
|
if (!IS_BGP_INST_KNOWN_TO_ZEBRA(bgp))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
s = zclient->obuf;
|
|
|
|
stream_reset(s);
|
|
|
|
|
|
|
|
zclient_create_header(s, ZEBRA_ADVERTISE_SUBNET, bgp->vrf_id);
|
|
|
|
stream_putc(s, advertise);
|
|
|
|
stream_put3(s, vni);
|
|
|
|
stream_putw_at(s, 0, stream_get_endp(s));
|
|
|
|
|
|
|
|
return zclient_send_message(zclient);
|
|
|
|
}
|
|
|
|
|
2017-06-28 10:51:10 +02:00
|
|
|
int bgp_zebra_advertise_gw_macip(struct bgp *bgp, int advertise, vni_t vni)
|
|
|
|
{
|
|
|
|
struct stream *s = NULL;
|
|
|
|
|
|
|
|
/* Check socket. */
|
|
|
|
if (!zclient || zclient->sock < 0)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
/* Don't try to register if Zebra doesn't know of this instance. */
|
|
|
|
if (!IS_BGP_INST_KNOWN_TO_ZEBRA(bgp))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
s = zclient->obuf;
|
|
|
|
stream_reset(s);
|
|
|
|
|
|
|
|
zclient_create_header(s, ZEBRA_ADVERTISE_DEFAULT_GW, bgp->vrf_id);
|
|
|
|
stream_putc(s, advertise);
|
2018-03-02 02:18:34 +01:00
|
|
|
stream_putl(s, vni);
|
2017-06-28 10:51:10 +02:00
|
|
|
stream_putw_at(s, 0, stream_get_endp(s));
|
|
|
|
|
|
|
|
return zclient_send_message(zclient);
|
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
int bgp_zebra_advertise_all_vni(struct bgp *bgp, int advertise)
|
2017-05-15 23:30:19 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct stream *s;
|
2017-05-15 23:30:19 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Check socket. */
|
|
|
|
if (!zclient || zclient->sock < 0)
|
|
|
|
return 0;
|
2017-05-15 23:30:19 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Don't try to register if Zebra doesn't know of this instance. */
|
|
|
|
if (!IS_BGP_INST_KNOWN_TO_ZEBRA(bgp))
|
|
|
|
return 0;
|
2017-05-15 23:30:19 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
s = zclient->obuf;
|
|
|
|
stream_reset(s);
|
2017-05-15 23:30:19 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
zclient_create_header(s, ZEBRA_ADVERTISE_ALL_VNI, bgp->vrf_id);
|
|
|
|
stream_putc(s, advertise);
|
|
|
|
stream_putw_at(s, 0, stream_get_endp(s));
|
2017-05-15 23:30:19 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
return zclient_send_message(zclient);
|
2017-05-15 23:30:19 +02:00
|
|
|
}
|
|
|
|
|
2018-03-08 15:39:19 +01:00
|
|
|
static int rule_notify_owner(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
|
|
|
{
|
|
|
|
uint32_t seqno, priority, unique;
|
|
|
|
enum zapi_rule_notify_owner note;
|
|
|
|
struct bgp_pbr_action *bgp_pbra;
|
|
|
|
ifindex_t ifi;
|
|
|
|
|
|
|
|
if (!zapi_rule_notify_decode(zclient->ibuf, &seqno, &priority, &unique,
|
|
|
|
&ifi, ¬e))
|
|
|
|
return -1;
|
|
|
|
|
2018-03-12 15:11:33 +01:00
|
|
|
bgp_pbra = bgp_pbr_action_rule_lookup(vrf_id, unique);
|
2018-03-08 15:39:19 +01:00
|
|
|
if (!bgp_pbra) {
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Fail to look BGP rule (%u)",
|
|
|
|
__PRETTY_FUNCTION__, unique);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (note) {
|
|
|
|
case ZAPI_RULE_FAIL_INSTALL:
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received RULE_FAIL_INSTALL",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
bgp_pbra->installed = false;
|
|
|
|
bgp_pbra->install_in_progress = false;
|
|
|
|
break;
|
|
|
|
case ZAPI_RULE_INSTALLED:
|
|
|
|
bgp_pbra->installed = true;
|
|
|
|
bgp_pbra->install_in_progress = false;
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received RULE_INSTALLED",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
break;
|
2018-05-18 18:15:47 +02:00
|
|
|
case ZAPI_RULE_FAIL_REMOVE:
|
2018-03-08 15:39:19 +01:00
|
|
|
case ZAPI_RULE_REMOVED:
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received RULE REMOVED",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ipset_notify_owner(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
|
|
|
{
|
|
|
|
uint32_t unique;
|
|
|
|
enum zapi_ipset_notify_owner note;
|
|
|
|
struct bgp_pbr_match *bgp_pbim;
|
|
|
|
|
|
|
|
if (!zapi_ipset_notify_decode(zclient->ibuf,
|
|
|
|
&unique,
|
|
|
|
¬e))
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
bgp_pbim = bgp_pbr_match_ipset_lookup(vrf_id, unique);
|
|
|
|
if (!bgp_pbim) {
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
2018-04-30 10:35:10 +02:00
|
|
|
zlog_debug("%s: Fail to look BGP match ( %u %u)",
|
|
|
|
__PRETTY_FUNCTION__, note, unique);
|
2018-03-08 15:39:19 +01:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (note) {
|
|
|
|
case ZAPI_IPSET_FAIL_INSTALL:
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPSET_FAIL_INSTALL",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
bgp_pbim->installed = false;
|
|
|
|
bgp_pbim->install_in_progress = false;
|
|
|
|
break;
|
|
|
|
case ZAPI_IPSET_INSTALLED:
|
|
|
|
bgp_pbim->installed = true;
|
|
|
|
bgp_pbim->install_in_progress = false;
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPSET_INSTALLED",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
break;
|
2018-05-18 18:15:47 +02:00
|
|
|
case ZAPI_IPSET_FAIL_REMOVE:
|
2018-03-08 15:39:19 +01:00
|
|
|
case ZAPI_IPSET_REMOVED:
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPSET REMOVED",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ipset_entry_notify_owner(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
|
|
|
{
|
|
|
|
uint32_t unique;
|
|
|
|
char ipset_name[ZEBRA_IPSET_NAME_SIZE];
|
|
|
|
enum zapi_ipset_entry_notify_owner note;
|
|
|
|
struct bgp_pbr_match_entry *bgp_pbime;
|
|
|
|
|
|
|
|
if (!zapi_ipset_entry_notify_decode(
|
|
|
|
zclient->ibuf,
|
|
|
|
&unique,
|
|
|
|
ipset_name,
|
|
|
|
¬e))
|
|
|
|
return -1;
|
|
|
|
bgp_pbime = bgp_pbr_match_ipset_entry_lookup(vrf_id,
|
|
|
|
ipset_name,
|
|
|
|
unique);
|
|
|
|
if (!bgp_pbime) {
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
2018-04-30 10:35:10 +02:00
|
|
|
zlog_debug("%s: Fail to look BGP match entry (%u %u)",
|
|
|
|
__PRETTY_FUNCTION__, note, unique);
|
2018-03-08 15:39:19 +01:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (note) {
|
|
|
|
case ZAPI_IPSET_ENTRY_FAIL_INSTALL:
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPSET_ENTRY_FAIL_INSTALL",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
bgp_pbime->installed = false;
|
|
|
|
bgp_pbime->install_in_progress = false;
|
|
|
|
break;
|
|
|
|
case ZAPI_IPSET_ENTRY_INSTALLED:
|
2018-04-20 11:41:54 +02:00
|
|
|
{
|
|
|
|
struct bgp_info *bgp_info;
|
|
|
|
struct bgp_info_extra *extra;
|
|
|
|
|
|
|
|
bgp_pbime->installed = true;
|
|
|
|
bgp_pbime->install_in_progress = false;
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPSET_ENTRY_INSTALLED",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
/* link bgp_info to bpme */
|
|
|
|
bgp_info = (struct bgp_info *)bgp_pbime->bgp_info;
|
|
|
|
extra = bgp_info_extra_get(bgp_info);
|
|
|
|
extra->bgp_fs_pbr = (void *)bgp_pbime;
|
|
|
|
}
|
2018-03-08 15:39:19 +01:00
|
|
|
break;
|
2018-05-18 18:15:47 +02:00
|
|
|
case ZAPI_IPSET_ENTRY_FAIL_REMOVE:
|
2018-03-08 15:39:19 +01:00
|
|
|
case ZAPI_IPSET_ENTRY_REMOVED:
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPSET_ENTRY_REMOVED",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-03-12 09:38:53 +01:00
|
|
|
static int iptable_notify_owner(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
|
|
|
{
|
|
|
|
uint32_t unique;
|
|
|
|
enum zapi_iptable_notify_owner note;
|
|
|
|
struct bgp_pbr_match *bgpm;
|
|
|
|
|
|
|
|
if (!zapi_iptable_notify_decode(
|
|
|
|
zclient->ibuf,
|
|
|
|
&unique,
|
|
|
|
¬e))
|
|
|
|
return -1;
|
|
|
|
bgpm = bgp_pbr_match_iptable_lookup(vrf_id, unique);
|
|
|
|
if (!bgpm) {
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
2018-04-30 10:35:10 +02:00
|
|
|
zlog_debug("%s: Fail to look BGP iptable (%u %u)",
|
|
|
|
__PRETTY_FUNCTION__, note, unique);
|
2018-03-12 09:38:53 +01:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
switch (note) {
|
|
|
|
case ZAPI_IPTABLE_FAIL_INSTALL:
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPTABLE_FAIL_INSTALL",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
bgpm->installed_in_iptable = false;
|
|
|
|
bgpm->install_iptable_in_progress = false;
|
|
|
|
break;
|
|
|
|
case ZAPI_IPTABLE_INSTALLED:
|
|
|
|
bgpm->installed_in_iptable = true;
|
|
|
|
bgpm->install_iptable_in_progress = false;
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPTABLE_INSTALLED",
|
|
|
|
__PRETTY_FUNCTION__);
|
2018-04-24 16:35:00 +02:00
|
|
|
bgpm->action->refcnt++;
|
2018-03-12 09:38:53 +01:00
|
|
|
break;
|
2018-05-18 18:15:47 +02:00
|
|
|
case ZAPI_IPTABLE_FAIL_REMOVE:
|
2018-03-12 09:38:53 +01:00
|
|
|
case ZAPI_IPTABLE_REMOVED:
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: Received IPTABLE REMOVED",
|
|
|
|
__PRETTY_FUNCTION__);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-03-08 15:39:19 +01:00
|
|
|
static void bgp_encode_pbr_rule_action(struct stream *s,
|
|
|
|
struct bgp_pbr_action *pbra)
|
|
|
|
{
|
|
|
|
struct prefix any;
|
|
|
|
|
|
|
|
stream_putl(s, 0); /* seqno unused */
|
|
|
|
stream_putl(s, 0); /* ruleno unused */
|
|
|
|
|
|
|
|
stream_putl(s, pbra->unique);
|
|
|
|
|
|
|
|
memset(&any, 0, sizeof(any));
|
|
|
|
any.family = AF_INET;
|
|
|
|
stream_putc(s, any.family);
|
|
|
|
stream_putc(s, any.prefixlen);
|
|
|
|
stream_put(s, &any.u.prefix, prefix_blen(&any));
|
|
|
|
|
|
|
|
stream_putw(s, 0); /* src port */
|
|
|
|
|
|
|
|
stream_putc(s, any.family);
|
|
|
|
stream_putc(s, any.prefixlen);
|
|
|
|
stream_put(s, &any.u.prefix, prefix_blen(&any));
|
|
|
|
|
|
|
|
stream_putw(s, 0); /* dst port */
|
|
|
|
|
|
|
|
stream_putl(s, pbra->fwmark); /* fwmark */
|
|
|
|
|
|
|
|
stream_putl(s, pbra->table_id);
|
|
|
|
|
|
|
|
stream_putl(s, 0); /* ifindex unused */
|
|
|
|
}
|
|
|
|
|
|
|
|
static void bgp_encode_pbr_ipset_match(struct stream *s,
|
|
|
|
struct bgp_pbr_match *pbim)
|
|
|
|
{
|
|
|
|
stream_putl(s, pbim->unique);
|
|
|
|
stream_putl(s, pbim->type);
|
|
|
|
|
|
|
|
stream_put(s, pbim->ipset_name,
|
|
|
|
ZEBRA_IPSET_NAME_SIZE);
|
|
|
|
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
static void bgp_encode_pbr_ipset_entry_match(struct stream *s,
|
|
|
|
struct bgp_pbr_match_entry *pbime)
|
|
|
|
{
|
|
|
|
stream_putl(s, pbime->unique);
|
|
|
|
/* check that back pointer is not null */
|
|
|
|
stream_put(s, pbime->backpointer->ipset_name,
|
|
|
|
ZEBRA_IPSET_NAME_SIZE);
|
|
|
|
|
|
|
|
stream_putc(s, pbime->src.family);
|
|
|
|
stream_putc(s, pbime->src.prefixlen);
|
|
|
|
stream_put(s, &pbime->src.u.prefix, prefix_blen(&pbime->src));
|
|
|
|
|
|
|
|
stream_putc(s, pbime->dst.family);
|
|
|
|
stream_putc(s, pbime->dst.prefixlen);
|
|
|
|
stream_put(s, &pbime->dst.u.prefix, prefix_blen(&pbime->dst));
|
2018-03-30 13:01:39 +02:00
|
|
|
|
|
|
|
stream_putw(s, pbime->src_port_min);
|
|
|
|
stream_putw(s, pbime->src_port_max);
|
|
|
|
stream_putw(s, pbime->dst_port_min);
|
|
|
|
stream_putw(s, pbime->dst_port_max);
|
|
|
|
stream_putc(s, pbime->proto);
|
2018-03-08 15:39:19 +01:00
|
|
|
}
|
|
|
|
|
2018-03-12 09:38:53 +01:00
|
|
|
static void bgp_encode_pbr_iptable_match(struct stream *s,
|
|
|
|
struct bgp_pbr_action *bpa,
|
|
|
|
struct bgp_pbr_match *pbm)
|
|
|
|
{
|
|
|
|
stream_putl(s, pbm->unique2);
|
|
|
|
|
|
|
|
stream_putl(s, pbm->type);
|
|
|
|
|
|
|
|
stream_putl(s, pbm->flags);
|
|
|
|
|
|
|
|
/* TODO: correlate with what is contained
|
|
|
|
* into bgp_pbr_action.
|
|
|
|
* currently only forward supported
|
|
|
|
*/
|
|
|
|
if (bpa->nh.type == NEXTHOP_TYPE_BLACKHOLE)
|
|
|
|
stream_putl(s, ZEBRA_IPTABLES_DROP);
|
|
|
|
else
|
|
|
|
stream_putl(s, ZEBRA_IPTABLES_FORWARD);
|
|
|
|
stream_putl(s, bpa->fwmark);
|
|
|
|
stream_put(s, pbm->ipset_name,
|
|
|
|
ZEBRA_IPSET_NAME_SIZE);
|
|
|
|
}
|
|
|
|
|
2016-02-12 21:18:28 +01:00
|
|
|
/* BGP has established connection with Zebra. */
|
2017-07-17 14:03:14 +02:00
|
|
|
static void bgp_zebra_connected(struct zclient *zclient)
|
*: add VRF ID in the API message header
The API messages are used by zebra to exchange the interfaces, addresses,
routes and router-id information with its clients. To distinguish which
VRF the information belongs to, a new field "VRF ID" is added in the
message header. And hence the message version is increased to 3.
* The new field "VRF ID" in the message header:
Length (2 bytes)
Marker (1 byte)
Version (1 byte)
VRF ID (2 bytes, newly added)
Command (2 bytes)
- Client side:
- zclient_create_header() adds the VRF ID in the message header.
- zclient_read() extracts and validates the VRF ID from the header,
and passes the VRF ID to the callback functions registered to
the API messages.
- All relative functions are appended with a new parameter "vrf_id",
including all the callback functions.
- "vrf_id" is also added to "struct zapi_ipv4" and "struct zapi_ipv6".
Clients need to correctly set the VRF ID when using the API
functions zapi_ipv4_route() and zapi_ipv6_route().
- Till now all messages sent from a client have the default VRF ID
"0" in the header.
- The HELLO message is special, which is used as the heart-beat of
a client, and has no relation with VRF. The VRF ID in the HELLO
message header will always be 0 and ignored by zebra.
- Zebra side:
- zserv_create_header() adds the VRF ID in the message header.
- zebra_client_read() extracts and validates the VRF ID from the
header, and passes the VRF ID to the functions which process
the received messages.
- All relative functions are appended with a new parameter "vrf_id".
* Suppress the messages in a VRF which a client does not care:
Some clients may not care about the information in the VRF X, and
zebra should not send the messages in the VRF X to those clients.
Extra flags are used to indicate which VRF is registered by a client,
and a new message ZEBRA_VRF_UNREGISTER is introduced to let a client
can unregister a VRF when it does not need any information in that
VRF.
A client sends any message other than ZEBRA_VRF_UNREGISTER in a VRF
will automatically register to that VRF.
- lib/vrf:
A new utility "VRF bit-map" is provided to manage the flags for
VRFs, one bit per VRF ID.
- Use vrf_bitmap_init()/vrf_bitmap_free() to initialize/free a
bit-map;
- Use vrf_bitmap_set()/vrf_bitmap_unset() to set/unset a flag
in the given bit-map, corresponding to the given VRF ID;
- Use vrf_bitmap_check() to test whether the flag, in the given
bit-map and for the given VRF ID, is set.
- Client side:
- In "struct zclient", the following flags are changed from
"u_char" to "vrf_bitmap_t":
redist[ZEBRA_ROUTE_MAX]
default_information
These flags are extended for each VRF, and controlled by the
clients themselves (or with the help of zclient_redistribute()
and zclient_redistribute_default()).
- Zebra side:
- In "struct zserv", the following flags are changed from
"u_char" to "vrf_bitmap_t":
redist[ZEBRA_ROUTE_MAX]
redist_default
ifinfo
ridinfo
These flags are extended for each VRF, as the VRF registration
flags. They are maintained on receiving a ZEBRA_XXX_ADD or
ZEBRA_XXX_DELETE message.
When sending an interface/address/route/router-id message in
a VRF to a client, if the corresponding VRF registration flag
is not set, this message will not be dropped by zebra.
- A new function zread_vrf_unregister() is introduced to process
the new command ZEBRA_VRF_UNREGISTER. All the VRF registration
flags are cleared for the requested VRF.
Those clients, who support only the default VRF, will never receive
a message in a non-default VRF, thanks to the filter in zebra.
* New callback for the event of successful connection to zebra:
- zclient_start() is splitted, keeping only the code of connecting
to zebra.
- Now zclient_init()=>zclient_connect()=>zclient_start() operations
are purely dealing with the connection to zbera.
- Once zebra is successfully connected, at the end of zclient_start(),
a new callback is used to inform the client about connection.
- Till now, in the callback of connect-to-zebra event, all clients
send messages to zebra to request the router-id/interface/routes
information in the default VRF.
Of corse in future the client can do anything it wants in this
callback. For example, it may send requests for both default VRF
and some non-default VRFs.
Signed-off-by: Feng Lu <lu.feng@6wind.com>
Reviewed-by: Alain Ritoux <alain.ritoux@6wind.com>
Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Acked-by: Donald Sharp <sharpd@cumulusnetworks.com>
Conflicts:
lib/zclient.h
lib/zebra.h
zebra/zserv.c
zebra/zserv.h
Conflicts:
bgpd/bgp_nexthop.c
bgpd/bgp_nht.c
bgpd/bgp_zebra.c
isisd/isis_zebra.c
lib/zclient.c
lib/zclient.h
lib/zebra.h
nhrpd/nhrp_interface.c
nhrpd/nhrp_route.c
nhrpd/nhrpd.h
ospf6d/ospf6_zebra.c
ospf6d/ospf6_zebra.h
ospfd/ospf_vty.c
ospfd/ospf_zebra.c
pimd/pim_zebra.c
pimd/pim_zlookup.c
ripd/rip_zebra.c
ripngd/ripng_zebra.c
zebra/redistribute.c
zebra/rt_netlink.c
zebra/zebra_rnh.c
zebra/zebra_rnh.h
zebra/zserv.c
zebra/zserv.h
2014-10-16 03:52:36 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct bgp *bgp;
|
*: add VRF ID in the API message header
The API messages are used by zebra to exchange the interfaces, addresses,
routes and router-id information with its clients. To distinguish which
VRF the information belongs to, a new field "VRF ID" is added in the
message header. And hence the message version is increased to 3.
* The new field "VRF ID" in the message header:
Length (2 bytes)
Marker (1 byte)
Version (1 byte)
VRF ID (2 bytes, newly added)
Command (2 bytes)
- Client side:
- zclient_create_header() adds the VRF ID in the message header.
- zclient_read() extracts and validates the VRF ID from the header,
and passes the VRF ID to the callback functions registered to
the API messages.
- All relative functions are appended with a new parameter "vrf_id",
including all the callback functions.
- "vrf_id" is also added to "struct zapi_ipv4" and "struct zapi_ipv6".
Clients need to correctly set the VRF ID when using the API
functions zapi_ipv4_route() and zapi_ipv6_route().
- Till now all messages sent from a client have the default VRF ID
"0" in the header.
- The HELLO message is special, which is used as the heart-beat of
a client, and has no relation with VRF. The VRF ID in the HELLO
message header will always be 0 and ignored by zebra.
- Zebra side:
- zserv_create_header() adds the VRF ID in the message header.
- zebra_client_read() extracts and validates the VRF ID from the
header, and passes the VRF ID to the functions which process
the received messages.
- All relative functions are appended with a new parameter "vrf_id".
* Suppress the messages in a VRF which a client does not care:
Some clients may not care about the information in the VRF X, and
zebra should not send the messages in the VRF X to those clients.
Extra flags are used to indicate which VRF is registered by a client,
and a new message ZEBRA_VRF_UNREGISTER is introduced to let a client
can unregister a VRF when it does not need any information in that
VRF.
A client sends any message other than ZEBRA_VRF_UNREGISTER in a VRF
will automatically register to that VRF.
- lib/vrf:
A new utility "VRF bit-map" is provided to manage the flags for
VRFs, one bit per VRF ID.
- Use vrf_bitmap_init()/vrf_bitmap_free() to initialize/free a
bit-map;
- Use vrf_bitmap_set()/vrf_bitmap_unset() to set/unset a flag
in the given bit-map, corresponding to the given VRF ID;
- Use vrf_bitmap_check() to test whether the flag, in the given
bit-map and for the given VRF ID, is set.
- Client side:
- In "struct zclient", the following flags are changed from
"u_char" to "vrf_bitmap_t":
redist[ZEBRA_ROUTE_MAX]
default_information
These flags are extended for each VRF, and controlled by the
clients themselves (or with the help of zclient_redistribute()
and zclient_redistribute_default()).
- Zebra side:
- In "struct zserv", the following flags are changed from
"u_char" to "vrf_bitmap_t":
redist[ZEBRA_ROUTE_MAX]
redist_default
ifinfo
ridinfo
These flags are extended for each VRF, as the VRF registration
flags. They are maintained on receiving a ZEBRA_XXX_ADD or
ZEBRA_XXX_DELETE message.
When sending an interface/address/route/router-id message in
a VRF to a client, if the corresponding VRF registration flag
is not set, this message will not be dropped by zebra.
- A new function zread_vrf_unregister() is introduced to process
the new command ZEBRA_VRF_UNREGISTER. All the VRF registration
flags are cleared for the requested VRF.
Those clients, who support only the default VRF, will never receive
a message in a non-default VRF, thanks to the filter in zebra.
* New callback for the event of successful connection to zebra:
- zclient_start() is splitted, keeping only the code of connecting
to zebra.
- Now zclient_init()=>zclient_connect()=>zclient_start() operations
are purely dealing with the connection to zbera.
- Once zebra is successfully connected, at the end of zclient_start(),
a new callback is used to inform the client about connection.
- Till now, in the callback of connect-to-zebra event, all clients
send messages to zebra to request the router-id/interface/routes
information in the default VRF.
Of corse in future the client can do anything it wants in this
callback. For example, it may send requests for both default VRF
and some non-default VRFs.
Signed-off-by: Feng Lu <lu.feng@6wind.com>
Reviewed-by: Alain Ritoux <alain.ritoux@6wind.com>
Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Acked-by: Donald Sharp <sharpd@cumulusnetworks.com>
Conflicts:
lib/zclient.h
lib/zebra.h
zebra/zserv.c
zebra/zserv.h
Conflicts:
bgpd/bgp_nexthop.c
bgpd/bgp_nht.c
bgpd/bgp_zebra.c
isisd/isis_zebra.c
lib/zclient.c
lib/zclient.h
lib/zebra.h
nhrpd/nhrp_interface.c
nhrpd/nhrp_route.c
nhrpd/nhrpd.h
ospf6d/ospf6_zebra.c
ospf6d/ospf6_zebra.h
ospfd/ospf_vty.c
ospfd/ospf_zebra.c
pimd/pim_zebra.c
pimd/pim_zlookup.c
ripd/rip_zebra.c
ripngd/ripng_zebra.c
zebra/redistribute.c
zebra/rt_netlink.c
zebra/zebra_rnh.c
zebra/zebra_rnh.h
zebra/zserv.c
zebra/zserv.h
2014-10-16 03:52:36 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
zclient_num_connects++; /* increment even if not responding */
|
2016-10-07 15:44:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* At this point, we may or may not have BGP instances configured, but
|
|
|
|
* we're only interested in the default VRF (others wouldn't have learnt
|
|
|
|
* the VRF from Zebra yet.)
|
|
|
|
*/
|
|
|
|
bgp = bgp_get_default();
|
|
|
|
if (!bgp)
|
|
|
|
return;
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp_zebra_instance_register(bgp);
|
2016-02-12 21:18:28 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* Send the client registration */
|
|
|
|
bfd_client_sendmsg(zclient, ZEBRA_BFD_CLIENT_REGISTER);
|
2016-06-21 12:39:58 +02:00
|
|
|
|
2018-04-07 20:13:07 +02:00
|
|
|
/* tell label pool that zebra is connected */
|
2018-04-07 20:32:52 +02:00
|
|
|
bgp_lp_event_zebra_up();
|
2018-04-07 20:13:07 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
/* TODO - What if we have peers and networks configured, do we have to
|
|
|
|
* kick-start them?
|
|
|
|
*/
|
*: add VRF ID in the API message header
The API messages are used by zebra to exchange the interfaces, addresses,
routes and router-id information with its clients. To distinguish which
VRF the information belongs to, a new field "VRF ID" is added in the
message header. And hence the message version is increased to 3.
* The new field "VRF ID" in the message header:
Length (2 bytes)
Marker (1 byte)
Version (1 byte)
VRF ID (2 bytes, newly added)
Command (2 bytes)
- Client side:
- zclient_create_header() adds the VRF ID in the message header.
- zclient_read() extracts and validates the VRF ID from the header,
and passes the VRF ID to the callback functions registered to
the API messages.
- All relative functions are appended with a new parameter "vrf_id",
including all the callback functions.
- "vrf_id" is also added to "struct zapi_ipv4" and "struct zapi_ipv6".
Clients need to correctly set the VRF ID when using the API
functions zapi_ipv4_route() and zapi_ipv6_route().
- Till now all messages sent from a client have the default VRF ID
"0" in the header.
- The HELLO message is special, which is used as the heart-beat of
a client, and has no relation with VRF. The VRF ID in the HELLO
message header will always be 0 and ignored by zebra.
- Zebra side:
- zserv_create_header() adds the VRF ID in the message header.
- zebra_client_read() extracts and validates the VRF ID from the
header, and passes the VRF ID to the functions which process
the received messages.
- All relative functions are appended with a new parameter "vrf_id".
* Suppress the messages in a VRF which a client does not care:
Some clients may not care about the information in the VRF X, and
zebra should not send the messages in the VRF X to those clients.
Extra flags are used to indicate which VRF is registered by a client,
and a new message ZEBRA_VRF_UNREGISTER is introduced to let a client
can unregister a VRF when it does not need any information in that
VRF.
A client sends any message other than ZEBRA_VRF_UNREGISTER in a VRF
will automatically register to that VRF.
- lib/vrf:
A new utility "VRF bit-map" is provided to manage the flags for
VRFs, one bit per VRF ID.
- Use vrf_bitmap_init()/vrf_bitmap_free() to initialize/free a
bit-map;
- Use vrf_bitmap_set()/vrf_bitmap_unset() to set/unset a flag
in the given bit-map, corresponding to the given VRF ID;
- Use vrf_bitmap_check() to test whether the flag, in the given
bit-map and for the given VRF ID, is set.
- Client side:
- In "struct zclient", the following flags are changed from
"u_char" to "vrf_bitmap_t":
redist[ZEBRA_ROUTE_MAX]
default_information
These flags are extended for each VRF, and controlled by the
clients themselves (or with the help of zclient_redistribute()
and zclient_redistribute_default()).
- Zebra side:
- In "struct zserv", the following flags are changed from
"u_char" to "vrf_bitmap_t":
redist[ZEBRA_ROUTE_MAX]
redist_default
ifinfo
ridinfo
These flags are extended for each VRF, as the VRF registration
flags. They are maintained on receiving a ZEBRA_XXX_ADD or
ZEBRA_XXX_DELETE message.
When sending an interface/address/route/router-id message in
a VRF to a client, if the corresponding VRF registration flag
is not set, this message will not be dropped by zebra.
- A new function zread_vrf_unregister() is introduced to process
the new command ZEBRA_VRF_UNREGISTER. All the VRF registration
flags are cleared for the requested VRF.
Those clients, who support only the default VRF, will never receive
a message in a non-default VRF, thanks to the filter in zebra.
* New callback for the event of successful connection to zebra:
- zclient_start() is splitted, keeping only the code of connecting
to zebra.
- Now zclient_init()=>zclient_connect()=>zclient_start() operations
are purely dealing with the connection to zbera.
- Once zebra is successfully connected, at the end of zclient_start(),
a new callback is used to inform the client about connection.
- Till now, in the callback of connect-to-zebra event, all clients
send messages to zebra to request the router-id/interface/routes
information in the default VRF.
Of corse in future the client can do anything it wants in this
callback. For example, it may send requests for both default VRF
and some non-default VRFs.
Signed-off-by: Feng Lu <lu.feng@6wind.com>
Reviewed-by: Alain Ritoux <alain.ritoux@6wind.com>
Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Acked-by: Donald Sharp <sharpd@cumulusnetworks.com>
Conflicts:
lib/zclient.h
lib/zebra.h
zebra/zserv.c
zebra/zserv.h
Conflicts:
bgpd/bgp_nexthop.c
bgpd/bgp_nht.c
bgpd/bgp_zebra.c
isisd/isis_zebra.c
lib/zclient.c
lib/zclient.h
lib/zebra.h
nhrpd/nhrp_interface.c
nhrpd/nhrp_route.c
nhrpd/nhrpd.h
ospf6d/ospf6_zebra.c
ospf6d/ospf6_zebra.h
ospfd/ospf_vty.c
ospfd/ospf_zebra.c
pimd/pim_zebra.c
pimd/pim_zlookup.c
ripd/rip_zebra.c
ripngd/ripng_zebra.c
zebra/redistribute.c
zebra/rt_netlink.c
zebra/zebra_rnh.c
zebra/zebra_rnh.h
zebra/zserv.c
zebra/zserv.h
2014-10-16 03:52:36 +02:00
|
|
|
}
|
|
|
|
|
2017-10-09 02:46:08 +02:00
|
|
|
static int bgp_zebra_process_local_l3vni(int cmd, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
|
|
|
{
|
2018-02-06 23:28:22 +01:00
|
|
|
int filter = 0;
|
2017-10-09 02:46:08 +02:00
|
|
|
char buf[ETHER_ADDR_STRLEN];
|
2017-10-31 00:58:15 +01:00
|
|
|
vni_t l3vni = 0;
|
2017-10-09 02:46:08 +02:00
|
|
|
struct ethaddr rmac;
|
2017-10-31 00:58:15 +01:00
|
|
|
struct in_addr originator_ip;
|
2017-10-09 02:46:08 +02:00
|
|
|
struct stream *s;
|
|
|
|
|
|
|
|
memset(&rmac, 0, sizeof(struct ethaddr));
|
2017-10-31 00:58:15 +01:00
|
|
|
memset(&originator_ip, 0, sizeof(struct in_addr));
|
2017-10-09 02:46:08 +02:00
|
|
|
s = zclient->ibuf;
|
|
|
|
l3vni = stream_getl(s);
|
2017-10-31 00:58:15 +01:00
|
|
|
if (cmd == ZEBRA_L3VNI_ADD) {
|
2017-10-09 02:46:08 +02:00
|
|
|
stream_get(&rmac, s, sizeof(struct ethaddr));
|
2017-10-31 00:58:15 +01:00
|
|
|
originator_ip.s_addr = stream_get_ipv4(s);
|
2018-02-06 23:28:22 +01:00
|
|
|
stream_get(&filter, s, sizeof(int));
|
2017-10-31 00:58:15 +01:00
|
|
|
}
|
2017-10-09 02:46:08 +02:00
|
|
|
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
2018-02-06 23:28:22 +01:00
|
|
|
zlog_debug("Rx L3-VNI %s VRF %s VNI %u RMAC %s filter %s",
|
2017-10-09 02:46:08 +02:00
|
|
|
(cmd == ZEBRA_L3VNI_ADD) ? "add" : "del",
|
2018-03-06 20:02:52 +01:00
|
|
|
vrf_id_to_name(vrf_id), l3vni,
|
2018-02-06 23:28:22 +01:00
|
|
|
prefix_mac2str(&rmac, buf, sizeof(buf)),
|
|
|
|
filter ? "prefix-routes-only" : "none");
|
2017-10-09 02:46:08 +02:00
|
|
|
|
|
|
|
if (cmd == ZEBRA_L3VNI_ADD)
|
2018-02-06 23:28:22 +01:00
|
|
|
bgp_evpn_local_l3vni_add(l3vni, vrf_id, &rmac, originator_ip,
|
|
|
|
filter);
|
2017-10-09 02:46:08 +02:00
|
|
|
else
|
|
|
|
bgp_evpn_local_l3vni_del(l3vni, vrf_id);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_zebra_process_local_vni(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2017-05-15 23:34:04 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct stream *s;
|
|
|
|
vni_t vni;
|
|
|
|
struct bgp *bgp;
|
2018-02-09 19:22:50 +01:00
|
|
|
struct in_addr vtep_ip = {INADDR_ANY};
|
2017-10-08 05:26:16 +02:00
|
|
|
vrf_id_t tenant_vrf_id = VRF_DEFAULT;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
|
|
|
s = zclient->ibuf;
|
|
|
|
vni = stream_getl(s);
|
2017-10-08 05:26:16 +02:00
|
|
|
if (command == ZEBRA_VNI_ADD) {
|
2017-07-17 14:03:14 +02:00
|
|
|
vtep_ip.s_addr = stream_get_ipv4(s);
|
2017-10-08 05:26:16 +02:00
|
|
|
stream_get(&tenant_vrf_id, s, sizeof(vrf_id_t));
|
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
2017-10-08 05:26:16 +02:00
|
|
|
zlog_debug("Rx VNI %s VRF %s VNI %u tenant-vrf %s",
|
|
|
|
(command == ZEBRA_VNI_ADD) ? "add" : "del",
|
2018-02-09 19:22:50 +01:00
|
|
|
vrf_id_to_name(vrf_id), vni,
|
|
|
|
vrf_id_to_name(tenant_vrf_id));
|
2017-07-17 14:03:14 +02:00
|
|
|
|
|
|
|
if (command == ZEBRA_VNI_ADD)
|
|
|
|
return bgp_evpn_local_vni_add(
|
2017-10-08 05:26:16 +02:00
|
|
|
bgp, vni, vtep_ip.s_addr ? vtep_ip : bgp->router_id,
|
|
|
|
tenant_vrf_id);
|
2017-07-17 14:03:14 +02:00
|
|
|
else
|
|
|
|
return bgp_evpn_local_vni_del(bgp, vni);
|
2017-05-15 23:34:04 +02:00
|
|
|
}
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
static int bgp_zebra_process_local_macip(int command, struct zclient *zclient,
|
|
|
|
zebra_size_t length, vrf_id_t vrf_id)
|
2017-05-15 23:34:04 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
struct stream *s;
|
|
|
|
vni_t vni;
|
|
|
|
struct bgp *bgp;
|
|
|
|
struct ethaddr mac;
|
|
|
|
struct ipaddr ip;
|
|
|
|
int ipa_len;
|
|
|
|
char buf[ETHER_ADDR_STRLEN];
|
|
|
|
char buf1[INET6_ADDRSTRLEN];
|
2018-03-27 21:13:34 +02:00
|
|
|
uint8_t flags;
|
2017-07-17 14:03:14 +02:00
|
|
|
|
|
|
|
memset(&ip, 0, sizeof(ip));
|
|
|
|
s = zclient->ibuf;
|
|
|
|
vni = stream_getl(s);
|
2017-08-03 14:45:27 +02:00
|
|
|
stream_get(&mac.octet, s, ETH_ALEN);
|
2017-07-17 14:03:14 +02:00
|
|
|
ipa_len = stream_getl(s);
|
|
|
|
if (ipa_len != 0 && ipa_len != IPV4_MAX_BYTELEN
|
|
|
|
&& ipa_len != IPV6_MAX_BYTELEN) {
|
|
|
|
zlog_err("%u:Recv MACIP %s with invalid IP addr length %d",
|
|
|
|
vrf_id, (command == ZEBRA_MACIP_ADD) ? "Add" : "Del",
|
|
|
|
ipa_len);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ipa_len) {
|
|
|
|
ip.ipa_type =
|
|
|
|
(ipa_len == IPV4_MAX_BYTELEN) ? IPADDR_V4 : IPADDR_V6;
|
|
|
|
stream_get(&ip.ip.addr, s, ipa_len);
|
|
|
|
}
|
2017-06-28 10:51:10 +02:00
|
|
|
flags = stream_getc(s);
|
2017-07-17 14:03:14 +02:00
|
|
|
|
|
|
|
bgp = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
2017-06-28 10:51:10 +02:00
|
|
|
zlog_debug("%u:Recv MACIP %s flags 0x%x MAC %s IP %s VNI %u",
|
|
|
|
vrf_id, (command == ZEBRA_MACIP_ADD) ? "Add" : "Del",
|
|
|
|
flags, prefix_mac2str(&mac, buf, sizeof(buf)),
|
2017-07-17 14:03:14 +02:00
|
|
|
ipaddr2str(&ip, buf1, sizeof(buf1)), vni);
|
|
|
|
|
|
|
|
if (command == ZEBRA_MACIP_ADD)
|
2017-06-28 10:51:10 +02:00
|
|
|
return bgp_evpn_local_macip_add(bgp, vni, &mac, &ip, flags);
|
2017-07-17 14:03:14 +02:00
|
|
|
else
|
|
|
|
return bgp_evpn_local_macip_del(bgp, vni, &mac, &ip);
|
2017-05-15 23:34:04 +02:00
|
|
|
}
|
2016-02-02 13:36:20 +01:00
|
|
|
|
2018-02-09 19:22:50 +01:00
|
|
|
static void bgp_zebra_process_local_ip_prefix(int cmd, struct zclient *zclient,
|
2017-11-20 06:47:04 +01:00
|
|
|
zebra_size_t length,
|
|
|
|
vrf_id_t vrf_id)
|
|
|
|
{
|
|
|
|
struct stream *s = NULL;
|
|
|
|
struct bgp *bgp_vrf = NULL;
|
|
|
|
struct prefix p;
|
|
|
|
char buf[PREFIX_STRLEN];
|
|
|
|
|
|
|
|
memset(&p, 0, sizeof(struct prefix));
|
|
|
|
s = zclient->ibuf;
|
|
|
|
stream_get(&p, s, sizeof(struct prefix));
|
|
|
|
|
|
|
|
bgp_vrf = bgp_lookup_by_vrf_id(vrf_id);
|
|
|
|
if (!bgp_vrf)
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("Recv prefix %s %s on vrf %s",
|
|
|
|
prefix2str(&p, buf, sizeof(buf)),
|
|
|
|
(cmd == ZEBRA_IP_PREFIX_ROUTE_ADD) ? "ADD" : "DEL",
|
|
|
|
vrf_id_to_name(vrf_id));
|
|
|
|
|
|
|
|
if (cmd == ZEBRA_IP_PREFIX_ROUTE_ADD) {
|
|
|
|
|
|
|
|
if (p.family == AF_INET)
|
2018-02-09 19:22:50 +01:00
|
|
|
return bgp_evpn_advertise_type5_route(
|
|
|
|
bgp_vrf, &p, NULL, AFI_IP, SAFI_UNICAST);
|
2017-11-20 06:47:04 +01:00
|
|
|
else
|
2018-02-09 19:22:50 +01:00
|
|
|
return bgp_evpn_advertise_type5_route(
|
|
|
|
bgp_vrf, &p, NULL, AFI_IP6, SAFI_UNICAST);
|
2017-11-20 06:47:04 +01:00
|
|
|
|
|
|
|
} else {
|
|
|
|
if (p.family == AF_INET)
|
2018-02-09 19:22:50 +01:00
|
|
|
return bgp_evpn_withdraw_type5_route(
|
|
|
|
bgp_vrf, &p, AFI_IP, SAFI_UNICAST);
|
2017-11-20 06:47:04 +01:00
|
|
|
else
|
2018-02-09 19:22:50 +01:00
|
|
|
return bgp_evpn_withdraw_type5_route(
|
|
|
|
bgp_vrf, &p, AFI_IP6, SAFI_UNICAST);
|
2017-11-20 06:47:04 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-04-07 20:13:07 +02:00
|
|
|
static void bgp_zebra_process_label_chunk(
|
|
|
|
int cmd,
|
|
|
|
struct zclient *zclient,
|
|
|
|
zebra_size_t length,
|
|
|
|
vrf_id_t vrf_id)
|
|
|
|
{
|
|
|
|
struct stream *s = NULL;
|
|
|
|
uint8_t response_keep;
|
|
|
|
uint32_t first;
|
|
|
|
uint32_t last;
|
2018-05-02 16:30:26 +02:00
|
|
|
uint8_t proto;
|
|
|
|
unsigned short instance;
|
2018-04-07 20:13:07 +02:00
|
|
|
|
|
|
|
s = zclient->ibuf;
|
2018-05-02 16:30:26 +02:00
|
|
|
STREAM_GETC(s, proto);
|
|
|
|
STREAM_GETW(s, instance);
|
2018-04-07 20:13:07 +02:00
|
|
|
STREAM_GETC(s, response_keep);
|
|
|
|
STREAM_GETL(s, first);
|
|
|
|
STREAM_GETL(s, last);
|
|
|
|
|
2018-05-02 16:30:26 +02:00
|
|
|
if (zclient->redist_default != proto) {
|
|
|
|
zlog_err("Got LM msg with wrong proto %u", proto);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
if (zclient->instance != instance) {
|
|
|
|
zlog_err("Got LM msg with wrong instance %u", proto);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2018-04-07 20:13:07 +02:00
|
|
|
if (first > last ||
|
|
|
|
first < MPLS_LABEL_UNRESERVED_MIN ||
|
|
|
|
last > MPLS_LABEL_UNRESERVED_MAX) {
|
|
|
|
|
|
|
|
zlog_err("%s: Invalid Label chunk: %u - %u",
|
|
|
|
__func__, first, last);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA)) {
|
|
|
|
zlog_debug("Label Chunk assign: %u - %u (%u) ",
|
|
|
|
first, last, response_keep);
|
|
|
|
}
|
|
|
|
|
2018-04-07 20:32:52 +02:00
|
|
|
bgp_lp_event_chunk(response_keep, first, last);
|
2018-04-07 20:13:07 +02:00
|
|
|
|
|
|
|
stream_failure: /* for STREAM_GETX */
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2017-10-11 16:37:20 +02:00
|
|
|
extern struct zebra_privs_t bgpd_privs;
|
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zebra_init(struct thread_master *master)
|
2002-12-13 21:15:29 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
zclient_num_connects = 0;
|
|
|
|
|
|
|
|
/* Set default values. */
|
2017-11-09 20:34:42 +01:00
|
|
|
zclient = zclient_new_notify(master, &zclient_options_default);
|
2017-10-11 16:37:20 +02:00
|
|
|
zclient_init(zclient, ZEBRA_ROUTE_BGP, 0, &bgpd_privs);
|
2017-07-17 14:03:14 +02:00
|
|
|
zclient->zebra_connected = bgp_zebra_connected;
|
|
|
|
zclient->router_id_update = bgp_router_id_update;
|
|
|
|
zclient->interface_add = bgp_interface_add;
|
|
|
|
zclient->interface_delete = bgp_interface_delete;
|
|
|
|
zclient->interface_address_add = bgp_interface_address_add;
|
|
|
|
zclient->interface_address_delete = bgp_interface_address_delete;
|
|
|
|
zclient->interface_nbr_address_add = bgp_interface_nbr_address_add;
|
|
|
|
zclient->interface_nbr_address_delete =
|
|
|
|
bgp_interface_nbr_address_delete;
|
|
|
|
zclient->interface_vrf_update = bgp_interface_vrf_update;
|
2017-08-21 03:10:50 +02:00
|
|
|
zclient->redistribute_route_add = zebra_read_route;
|
|
|
|
zclient->redistribute_route_del = zebra_read_route;
|
2017-07-17 14:03:14 +02:00
|
|
|
zclient->interface_up = bgp_interface_up;
|
|
|
|
zclient->interface_down = bgp_interface_down;
|
|
|
|
zclient->nexthop_update = bgp_read_nexthop_update;
|
|
|
|
zclient->import_check_update = bgp_read_import_check_update;
|
|
|
|
zclient->fec_update = bgp_read_fec_update;
|
|
|
|
zclient->local_vni_add = bgp_zebra_process_local_vni;
|
|
|
|
zclient->local_vni_del = bgp_zebra_process_local_vni;
|
|
|
|
zclient->local_macip_add = bgp_zebra_process_local_macip;
|
|
|
|
zclient->local_macip_del = bgp_zebra_process_local_macip;
|
2017-10-09 02:46:08 +02:00
|
|
|
zclient->local_l3vni_add = bgp_zebra_process_local_l3vni;
|
|
|
|
zclient->local_l3vni_del = bgp_zebra_process_local_l3vni;
|
2017-11-20 06:47:04 +01:00
|
|
|
zclient->local_ip_prefix_add = bgp_zebra_process_local_ip_prefix;
|
|
|
|
zclient->local_ip_prefix_del = bgp_zebra_process_local_ip_prefix;
|
2018-04-07 20:13:07 +02:00
|
|
|
zclient->label_chunk = bgp_zebra_process_label_chunk;
|
2018-03-08 15:39:19 +01:00
|
|
|
zclient->rule_notify_owner = rule_notify_owner;
|
|
|
|
zclient->ipset_notify_owner = ipset_notify_owner;
|
|
|
|
zclient->ipset_entry_notify_owner = ipset_entry_notify_owner;
|
2018-03-12 09:38:53 +01:00
|
|
|
zclient->iptable_notify_owner = iptable_notify_owner;
|
2002-12-13 21:15:29 +01:00
|
|
|
}
|
2016-01-12 19:41:57 +01:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
void bgp_zebra_destroy(void)
|
2016-01-12 19:41:57 +01:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
if (zclient == NULL)
|
|
|
|
return;
|
|
|
|
zclient_stop(zclient);
|
|
|
|
zclient_free(zclient);
|
|
|
|
zclient = NULL;
|
2016-01-12 19:41:57 +01:00
|
|
|
}
|
2016-10-07 15:44:42 +02:00
|
|
|
|
2017-07-17 14:03:14 +02:00
|
|
|
int bgp_zebra_num_connects(void)
|
2016-10-07 15:44:42 +02:00
|
|
|
{
|
2017-07-17 14:03:14 +02:00
|
|
|
return zclient_num_connects;
|
2016-10-07 15:44:42 +02:00
|
|
|
}
|
2018-03-08 15:39:19 +01:00
|
|
|
|
|
|
|
void bgp_send_pbr_rule_action(struct bgp_pbr_action *pbra, bool install)
|
|
|
|
{
|
|
|
|
struct stream *s;
|
|
|
|
|
|
|
|
if (pbra->install_in_progress)
|
|
|
|
return;
|
2018-05-21 12:02:52 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: table %d fwmark %d %d",
|
|
|
|
__PRETTY_FUNCTION__,
|
|
|
|
pbra->table_id, pbra->fwmark, install);
|
2018-03-08 15:39:19 +01:00
|
|
|
s = zclient->obuf;
|
|
|
|
stream_reset(s);
|
|
|
|
|
|
|
|
zclient_create_header(s,
|
|
|
|
install ? ZEBRA_RULE_ADD : ZEBRA_RULE_DELETE,
|
|
|
|
VRF_DEFAULT);
|
|
|
|
stream_putl(s, 1); /* send one pbr action */
|
|
|
|
|
|
|
|
bgp_encode_pbr_rule_action(s, pbra);
|
|
|
|
|
|
|
|
stream_putw_at(s, 0, stream_get_endp(s));
|
|
|
|
if (!zclient_send_message(zclient) && install)
|
|
|
|
pbra->install_in_progress = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
void bgp_send_pbr_ipset_match(struct bgp_pbr_match *pbrim, bool install)
|
|
|
|
{
|
|
|
|
struct stream *s;
|
|
|
|
|
|
|
|
if (pbrim->install_in_progress)
|
|
|
|
return;
|
2018-05-21 12:02:52 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: name %s type %d %d",
|
|
|
|
__PRETTY_FUNCTION__,
|
|
|
|
pbrim->ipset_name, pbrim->type, install);
|
2018-03-08 15:39:19 +01:00
|
|
|
s = zclient->obuf;
|
|
|
|
stream_reset(s);
|
|
|
|
|
|
|
|
zclient_create_header(s,
|
|
|
|
install ? ZEBRA_IPSET_CREATE :
|
|
|
|
ZEBRA_IPSET_DESTROY,
|
|
|
|
VRF_DEFAULT);
|
|
|
|
|
|
|
|
stream_putl(s, 1); /* send one pbr action */
|
|
|
|
|
|
|
|
bgp_encode_pbr_ipset_match(s, pbrim);
|
|
|
|
|
|
|
|
stream_putw_at(s, 0, stream_get_endp(s));
|
|
|
|
if (!zclient_send_message(zclient) && install)
|
|
|
|
pbrim->install_in_progress = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
void bgp_send_pbr_ipset_entry_match(struct bgp_pbr_match_entry *pbrime,
|
|
|
|
bool install)
|
|
|
|
{
|
|
|
|
struct stream *s;
|
|
|
|
|
|
|
|
if (pbrime->install_in_progress)
|
|
|
|
return;
|
2018-05-21 12:02:52 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: name %s %d %d", __PRETTY_FUNCTION__,
|
|
|
|
pbrime->backpointer->ipset_name,
|
|
|
|
pbrime->unique, install);
|
2018-03-08 15:39:19 +01:00
|
|
|
s = zclient->obuf;
|
|
|
|
stream_reset(s);
|
|
|
|
|
|
|
|
zclient_create_header(s,
|
|
|
|
install ? ZEBRA_IPSET_ENTRY_ADD :
|
|
|
|
ZEBRA_IPSET_ENTRY_DELETE,
|
|
|
|
VRF_DEFAULT);
|
|
|
|
|
|
|
|
stream_putl(s, 1); /* send one pbr action */
|
|
|
|
|
|
|
|
bgp_encode_pbr_ipset_entry_match(s, pbrime);
|
|
|
|
|
|
|
|
stream_putw_at(s, 0, stream_get_endp(s));
|
|
|
|
if (!zclient_send_message(zclient) && install)
|
|
|
|
pbrime->install_in_progress = true;
|
|
|
|
}
|
2018-03-12 09:38:53 +01:00
|
|
|
|
2018-04-25 18:29:35 +02:00
|
|
|
static void bgp_encode_pbr_interface_list(struct bgp *bgp, struct stream *s)
|
|
|
|
{
|
|
|
|
struct bgp_pbr_config *bgp_pbr_cfg = bgp->bgp_pbr_cfg;
|
|
|
|
struct bgp_pbr_interface_head *head;
|
|
|
|
struct bgp_pbr_interface *pbr_if;
|
|
|
|
struct interface *ifp;
|
|
|
|
|
|
|
|
if (!bgp_pbr_cfg)
|
|
|
|
return;
|
|
|
|
head = &(bgp_pbr_cfg->ifaces_by_name_ipv4);
|
|
|
|
|
|
|
|
RB_FOREACH (pbr_if, bgp_pbr_interface_head, head) {
|
|
|
|
ifp = if_lookup_by_name(pbr_if->name, bgp->vrf_id);
|
|
|
|
if (ifp)
|
|
|
|
stream_putl(s, ifp->ifindex);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static int bgp_pbr_get_ifnumber(struct bgp *bgp)
|
|
|
|
{
|
|
|
|
struct bgp_pbr_config *bgp_pbr_cfg = bgp->bgp_pbr_cfg;
|
|
|
|
struct bgp_pbr_interface_head *head;
|
|
|
|
struct bgp_pbr_interface *pbr_if;
|
|
|
|
int cnt = 0;
|
|
|
|
|
|
|
|
if (!bgp_pbr_cfg)
|
|
|
|
return 0;
|
|
|
|
head = &(bgp_pbr_cfg->ifaces_by_name_ipv4);
|
|
|
|
|
|
|
|
RB_FOREACH (pbr_if, bgp_pbr_interface_head, head) {
|
|
|
|
if (if_lookup_by_name(pbr_if->name, bgp->vrf_id))
|
|
|
|
cnt++;
|
|
|
|
}
|
|
|
|
return cnt;
|
|
|
|
}
|
|
|
|
|
2018-03-12 09:38:53 +01:00
|
|
|
void bgp_send_pbr_iptable(struct bgp_pbr_action *pba,
|
|
|
|
struct bgp_pbr_match *pbm,
|
|
|
|
bool install)
|
|
|
|
{
|
|
|
|
struct stream *s;
|
2018-05-18 16:14:46 +02:00
|
|
|
int ret = 0;
|
2018-04-25 18:29:35 +02:00
|
|
|
int nb_interface;
|
2018-03-12 09:38:53 +01:00
|
|
|
|
|
|
|
if (pbm->install_iptable_in_progress)
|
|
|
|
return;
|
2018-05-21 12:02:52 +02:00
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
|
|
|
zlog_debug("%s: name %s type %d mark %d %d",
|
|
|
|
__PRETTY_FUNCTION__, pbm->ipset_name,
|
|
|
|
pbm->type, pba->fwmark, install);
|
2018-03-12 09:38:53 +01:00
|
|
|
s = zclient->obuf;
|
|
|
|
stream_reset(s);
|
|
|
|
|
|
|
|
zclient_create_header(s,
|
|
|
|
install ? ZEBRA_IPTABLE_ADD :
|
|
|
|
ZEBRA_IPTABLE_DELETE,
|
|
|
|
VRF_DEFAULT);
|
|
|
|
|
|
|
|
bgp_encode_pbr_iptable_match(s, pba, pbm);
|
2018-04-25 18:29:35 +02:00
|
|
|
nb_interface = bgp_pbr_get_ifnumber(pba->bgp);
|
|
|
|
stream_putl(s, nb_interface);
|
|
|
|
if (nb_interface)
|
|
|
|
bgp_encode_pbr_interface_list(pba->bgp, s);
|
2018-03-12 09:38:53 +01:00
|
|
|
stream_putw_at(s, 0, stream_get_endp(s));
|
2018-05-18 16:14:46 +02:00
|
|
|
ret = zclient_send_message(zclient);
|
|
|
|
if (install) {
|
|
|
|
if (ret)
|
|
|
|
pba->refcnt++;
|
|
|
|
else
|
|
|
|
pbm->install_iptable_in_progress = true;
|
2018-04-24 16:35:00 +02:00
|
|
|
}
|
2018-03-12 09:38:53 +01:00
|
|
|
}
|
2018-03-28 14:51:57 +02:00
|
|
|
|
|
|
|
/* inject in table <table_id> a default route to:
|
|
|
|
* - if nexthop IP is present : to this nexthop
|
|
|
|
* - if vrf is different from local : to the matching VRF
|
|
|
|
*/
|
|
|
|
void bgp_zebra_announce_default(struct bgp *bgp, struct nexthop *nh,
|
|
|
|
afi_t afi, uint32_t table_id, bool announce)
|
|
|
|
{
|
|
|
|
struct zapi_nexthop *api_nh;
|
|
|
|
struct zapi_route api;
|
|
|
|
struct prefix p;
|
|
|
|
|
|
|
|
if (!nh || nh->type != NEXTHOP_TYPE_IPV4
|
|
|
|
|| nh->vrf_id == VRF_UNKNOWN)
|
|
|
|
return;
|
|
|
|
memset(&p, 0, sizeof(struct prefix));
|
|
|
|
/* default route */
|
|
|
|
if (afi != AFI_IP)
|
|
|
|
return;
|
|
|
|
p.family = AF_INET;
|
|
|
|
memset(&api, 0, sizeof(api));
|
|
|
|
api.vrf_id = bgp->vrf_id;
|
|
|
|
api.type = ZEBRA_ROUTE_BGP;
|
|
|
|
api.safi = SAFI_UNICAST;
|
|
|
|
api.prefix = p;
|
|
|
|
api.tableid = table_id;
|
|
|
|
api.nexthop_num = 1;
|
|
|
|
SET_FLAG(api.message, ZAPI_MESSAGE_TABLEID);
|
|
|
|
SET_FLAG(api.message, ZAPI_MESSAGE_NEXTHOP);
|
|
|
|
api_nh = &api.nexthops[0];
|
|
|
|
|
|
|
|
/* redirect IP */
|
|
|
|
if (nh->gate.ipv4.s_addr) {
|
|
|
|
char buff[PREFIX_STRLEN];
|
|
|
|
|
|
|
|
api_nh->vrf_id = nh->vrf_id;
|
|
|
|
api_nh->gate.ipv4 = nh->gate.ipv4;
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IPV4;
|
|
|
|
|
|
|
|
inet_ntop(AF_INET, &(nh->gate.ipv4), buff, INET_ADDRSTRLEN);
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
2018-05-21 18:35:38 +02:00
|
|
|
zlog_info("BGP: %s default route to %s table %d (redirect IP)",
|
|
|
|
announce ? "adding" : "withdrawing",
|
2018-03-28 14:51:57 +02:00
|
|
|
buff, table_id);
|
|
|
|
zclient_route_send(announce ? ZEBRA_ROUTE_ADD
|
|
|
|
: ZEBRA_ROUTE_DELETE,
|
|
|
|
zclient, &api);
|
|
|
|
} else if (nh->vrf_id != bgp->vrf_id) {
|
|
|
|
struct vrf *vrf;
|
2018-04-17 18:32:49 +02:00
|
|
|
struct interface *ifp;
|
2018-03-28 14:51:57 +02:00
|
|
|
|
2018-04-17 18:32:49 +02:00
|
|
|
vrf = vrf_lookup_by_id(nh->vrf_id);
|
2018-03-28 14:51:57 +02:00
|
|
|
if (!vrf)
|
|
|
|
return;
|
2018-04-17 18:32:49 +02:00
|
|
|
/* create default route with interface <VRF>
|
|
|
|
* with nexthop-vrf <VRF>
|
2018-03-28 14:51:57 +02:00
|
|
|
*/
|
2018-04-17 18:32:49 +02:00
|
|
|
ifp = if_lookup_by_name_all_vrf(vrf->name);
|
|
|
|
if (!ifp)
|
|
|
|
return;
|
|
|
|
api_nh->vrf_id = nh->vrf_id;
|
|
|
|
api_nh->type = NEXTHOP_TYPE_IFINDEX;
|
|
|
|
api_nh->ifindex = ifp->ifindex;
|
|
|
|
if (BGP_DEBUG(zebra, ZEBRA))
|
2018-05-21 18:35:38 +02:00
|
|
|
zlog_info("BGP: %s default route to %s table %d (redirect VRF)",
|
|
|
|
announce ? "adding" : "withdrawing",
|
2018-04-17 18:32:49 +02:00
|
|
|
vrf->name, table_id);
|
|
|
|
zclient_route_send(announce ? ZEBRA_ROUTE_ADD
|
|
|
|
: ZEBRA_ROUTE_DELETE,
|
|
|
|
zclient, &api);
|
2018-03-28 14:51:57 +02:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|