Files
vpp/src/plugins/linux-cp/lcp_nl.h
Pim van Pelt af4fa965e9 linux-cp: Fix add vs update on routes
Linux uses NLM_F_REPLACE in the netlink message to signal a FIB update
The code invariably does a FIB update for IPv4 and a addition for IPv6.
Without this fix, the following:
 ip route add 2001:db8::/48 via 2001:db8::1
 ip route replace 2001:db8::/48 via 2001:db8::2

ends up as two separate FIB entries in VPP. With the fix, there will be one FIB entry (the second one with nexthop ::2).

Type: fix
Change-Id: I8f98d6ded52ae0c60bfddaa7fc39acbbaa19d34a
Signed-off-by: Pim van Pelt <pim@ipng.nl>
2023-06-05 15:27:21 +00:00

162 lines
4.1 KiB
C

/*
* Copyright (c) 2019 Cisco and/or its affiliates.
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at:
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#include <vlib/vlib.h>
#include <netlink/route/link.h>
#include <netlink/route/route.h>
#include <netlink/route/neighbour.h>
#include <netlink/route/addr.h>
typedef void (*nl_rt_link_cb_t) (struct rtnl_link *rl, void *ctx);
typedef void (*nl_rt_link_sync_cb_t) (void);
typedef void (*nl_rt_addr_cb_t) (struct rtnl_addr *ra);
typedef void (*nl_rt_addr_sync_cb_t) (void);
typedef void (*nl_rt_neigh_cb_t) (struct rtnl_neigh *rr);
typedef void (*nl_rt_neigh_sync_cb_t) (void);
typedef void (*nl_rt_route_add_cb_t) (struct rtnl_route *rn, int is_replace);
typedef void (*nl_rt_route_del_cb_t) (struct rtnl_route *rn);
typedef void (*nl_rt_route_sync_cb_t) (void);
#define NL_RT_COMMON uword is_mp_safe
typedef struct nl_rt_link_t_
{
NL_RT_COMMON;
nl_rt_link_cb_t cb;
} nl_rt_link_t;
typedef struct nl_rt_link_sync_t_
{
NL_RT_COMMON;
nl_rt_link_sync_cb_t cb;
} nl_rt_link_sync_t;
typedef struct nl_rt_addr_t_
{
NL_RT_COMMON;
nl_rt_addr_cb_t cb;
} nl_rt_addr_t;
typedef struct nl_rt_addr_sync_t_
{
NL_RT_COMMON;
nl_rt_addr_sync_cb_t cb;
} nl_rt_addr_sync_t;
typedef struct nl_rt_neigh_t_
{
NL_RT_COMMON;
nl_rt_neigh_cb_t cb;
} nl_rt_neigh_t;
typedef struct nl_rt_neigh_sync_t_
{
NL_RT_COMMON;
nl_rt_neigh_sync_cb_t cb;
} nl_rt_neigh_sync_t;
typedef struct nl_rt_route_add_t_
{
NL_RT_COMMON;
nl_rt_route_add_cb_t cb;
} nl_rt_route_add_t;
typedef struct nl_rt_route_del_t_
{
NL_RT_COMMON;
nl_rt_route_del_cb_t cb;
} nl_rt_route_del_t;
typedef struct nl_rt_route_sync_t_
{
NL_RT_COMMON;
nl_rt_route_sync_cb_t cb;
} nl_rt_route_sync_t;
#undef NL_RT_COMMON
typedef struct nl_vft_t_
{
nl_rt_link_t nvl_rt_link_add;
nl_rt_link_t nvl_rt_link_del;
nl_rt_link_sync_t nvl_rt_link_sync_begin;
nl_rt_link_sync_t nvl_rt_link_sync_end;
nl_rt_addr_t nvl_rt_addr_add;
nl_rt_addr_t nvl_rt_addr_del;
nl_rt_addr_sync_t nvl_rt_addr_sync_begin;
nl_rt_addr_sync_t nvl_rt_addr_sync_end;
nl_rt_neigh_t nvl_rt_neigh_add;
nl_rt_neigh_t nvl_rt_neigh_del;
nl_rt_neigh_sync_t nvl_rt_neigh_sync_begin;
nl_rt_neigh_sync_t nvl_rt_neigh_sync_end;
nl_rt_route_add_t nvl_rt_route_add;
nl_rt_route_del_t nvl_rt_route_del;
nl_rt_route_sync_t nvl_rt_route_sync_begin;
nl_rt_route_sync_t nvl_rt_route_sync_end;
} nl_vft_t;
extern void nl_register_vft (const nl_vft_t *nv);
typedef enum lcp_nl_obj_t_
{
LCP_NL_LINK,
LCP_NL_ADDR,
LCP_NL_NEIGH,
LCP_NL_ROUTE,
} lcp_nl_obj_t;
/* struct type to hold context on the netlink message being processed.
*
* At creation of a pair, a tap/tun is created and configured to match its
* corresponding hardware interface (MAC address, link state, MTU). Netlink
* messages are sent announcing the creation and subsequent configuration.
* We do not need to (and should not) act on those messages since applying
* those same configurations again is unnecessary and can be disruptive. So
* a timestamp for a message is stored and can be compared against the time
* the interface came under linux-cp management in order to figure out
* whether we should apply any configuration.
*/
typedef struct nl_msg_info
{
struct nl_msg *msg;
f64 ts;
} nl_msg_info_t;
#define LCP_NL_N_OBJS (LCP_NL_ROUTE + 1)
extern struct nl_cache *lcp_nl_get_cache (lcp_nl_obj_t t);
extern int lcp_nl_drain_messages (void);
extern void lcp_nl_set_buffer_size (u32 buf_size);
extern void lcp_nl_set_batch_size (u32 batch_size);
extern void lcp_nl_set_batch_delay (u32 batch_delay_ms);
/*
* fd.io coding-style-patch-verification: ON
*
* Local Variables:
* eval: (c-set-style "gnu")
* End:
*/