diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2017-09-12 08:14:50 -0400 |
|---|---|---|
| committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2017-09-12 08:33:37 -0400 |
| commit | 1f1d24a8f1f183d6d0a4598b854b459f5b5d7e5c (patch) | |
| tree | 3e532999bac61a2d96f45f4c507ed933f6b7003c /python/clidef.py | |
| parent | 953d97fc4aef0c7715e8d42d7d52ebc18d873ac6 (diff) | |
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>
Diffstat (limited to 'python/clidef.py')
0 files changed, 0 insertions, 0 deletions
