diff options
| author | Sharath Ramamurthy <sramamurthy@nvidia.com> | 2021-07-27 21:59:00 +0530 |
|---|---|---|
| committer | Stephen Worley <sworley@nvidia.com> | 2023-02-13 18:12:04 -0500 |
| commit | 9464e5b865a2995e436ce2986f5722921cb83394 (patch) | |
| tree | 8f34095ac3893bb40922a063764b6b7b256a5991 /zebra/if_netlink.c | |
| parent | feffe4eea6d4f6e533a9c22917163fa34a2119b6 (diff) | |
zebra: Bug fixes in fdb read for flooded traffic and remote fdb cleanup upon vni removal
This patch addresses following issues,
- When the VLAN-VNI mapping is configured via a map and not using
individual VXLAN interfaces, upon removal of a VNI ensure that the
remote FDB entries are uninstalled correctly.
- When VNI configuration is performed using VLAN-VNI mapping (i.e., without
individual VXLAN interfaces) and flooded traffic is handled via multicast,
the multicast group corresponding to the VNI needs to be explicitly read
from the bridge FDB. This is relevant in the case of netlink interface to
the kernel and for the scenario where a new VNI is provisioned or comes up.
Signed-off-by: Sharath Ramamurthy <sramamurthy@nvidia.com>
Diffstat (limited to 'zebra/if_netlink.c')
| -rw-r--r-- | zebra/if_netlink.c | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/zebra/if_netlink.c b/zebra/if_netlink.c index 6375fc1bd0..c097e23777 100644 --- a/zebra/if_netlink.c +++ b/zebra/if_netlink.c @@ -629,8 +629,10 @@ static int netlink_extract_vxlan_info(struct rtattr *link_data, } if (!svd) { - /* in case of svd we will not get vni info directly from the - * device */ + /* + * In case of svd we will not get vni info directly from the + * device + */ if (!attr[IFLA_VXLAN_ID]) { if (IS_ZEBRA_DEBUG_KERNEL) zlog_debug( |