diff options
| author | 恭简 <gongjian.lhr@alibaba-inc.com> | 2023-07-26 09:51:51 +0800 |
|---|---|---|
| committer | 恭简 <gongjian.lhr@alibaba-inc.com> | 2023-08-01 09:58:00 +0800 |
| commit | 4aa1aace3e32039b668c04cd682b01e0397144ea (patch) | |
| tree | 18727c416502d93e3a6a91da1049aa9348c05653 | |
| parent | 3f043d027f29ec676b3abdc46397a863fbd73717 (diff) | |
zebra: remove duplicated nexthops when sending fpm msg
When zebra send msg to fpm client, it doesn't handle duplicated nexthops especially, which means if zebra has a route with NUM1 recursive nexthops, each resolved to the same NUM2 connected nexthops, it will send to fpm client a route with NUM1*NUM2 nexthops. But actually there are only NUM2 useful nexthops, the left NUM1*NUM2-NUM2 nexthops are all duplicated nexthops. By the way, zebra has duplicated nexthop remove logic when sending msg to kernel.
Add duplicated nexthop remove logic to zebra when sending msg to fpm client.
Signed-off-by: 恭简 <gongjian.lhr@alibaba-inc.com>
| -rw-r--r-- | zebra/zebra_fpm_netlink.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/zebra/zebra_fpm_netlink.c b/zebra/zebra_fpm_netlink.c index ba34951e76..1279762232 100644 --- a/zebra/zebra_fpm_netlink.c +++ b/zebra/zebra_fpm_netlink.c @@ -287,6 +287,8 @@ static int netlink_route_info_fill(struct netlink_route_info *ri, int cmd, if (CHECK_FLAG(nexthop->flags, NEXTHOP_FLAG_RECURSIVE)) continue; + if (CHECK_FLAG(nexthop->flags, NEXTHOP_FLAG_DUPLICATE)) + continue; if (nexthop->type == NEXTHOP_TYPE_BLACKHOLE) { switch (nexthop->bh_type) { |