diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2019-02-22 16:20:51 +0100 |
|---|---|---|
| committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2019-03-27 21:22:22 +0100 |
| commit | 9fb2b87997ac8a69133e5c157374eb2944671a27 (patch) | |
| tree | bd8c7f634fc1a82a4d580f9e4e057f93e261dc30 /ospf6d | |
| parent | zebra: Re-evaluate the nexthop tracking if flags changed (diff) | |
| download | frr-9fb2b87997ac8a69133e5c157374eb2944671a27.tar.xz frr-9fb2b87997ac8a69133e5c157374eb2944671a27.zip | |
isisd, ospf6d, ripngd: Do not allow v6 LL's to be `redist connected` in
The rib process of handling routes has been unified a bit more
and as a result v6 LL routes are now showing up as a result
of a `redistribute connected`. Doing anything with these
routes is a policy decision that should be enforced by the
individual routing daemons not by zebra. As such add a bit
of code to isisd, ripngd and opsf6d to handle them. The bgp daemon
already handles this situation.
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'ospf6d')
| -rw-r--r-- | ospf6d/ospf6_zebra.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/ospf6d/ospf6_zebra.c b/ospf6d/ospf6_zebra.c index 54f1735e7..abdc82a73 100644 --- a/ospf6d/ospf6_zebra.c +++ b/ospf6d/ospf6_zebra.c @@ -226,6 +226,9 @@ static int ospf6_zebra_read_route(int command, struct zclient *zclient, if (CHECK_FLAG(api.message, ZAPI_MESSAGE_SRCPFX)) return 0; + if (IN6_IS_ADDR_LINKLOCAL(&api.prefix.u.prefix6)) + return 0; + ifindex = api.nexthops[0].ifindex; nexthop = &api.nexthops[0].gate.ipv6; |