]> git.puffer.fish Git - mirror/frr.git/commit
zebra: Allow recursively resolved blackhole routes to be installed
authorDonald Sharp <sharpd@cumulusnetworks.com>
Tue, 12 Sep 2017 12:14:50 +0000 (08:14 -0400)
committerDonald Sharp <sharpd@cumulusnetworks.com>
Tue, 12 Sep 2017 12:33:37 +0000 (08:33 -0400)
commit1f1d24a8f1f183d6d0a4598b854b459f5b5d7e5c
tree3e532999bac61a2d96f45f4c507ed933f6b7003c
parent953d97fc4aef0c7715e8d42d7d52ebc18d873ac6
zebra: Allow recursively resolved blackhole routes to be installed

So the current code for a blackhole route assumed that you
would never want a recursively resolved blackhole to work.
Suppose you have this setup:

1) ip route 192.0.2.1/32 Null0
2) BGP installed with a route-map that rewrites the
   nexthop to 192.0.2.1.

Zebra will end up with a recursive nexthop that resolves
to the blackhole.

The original rib install function assumed that we would never
want the ability to recursively resolve a blackhole route.
Instead just handle the blackhole as part of the nexthop_num = 1
case.

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
zebra/rt_netlink.c