Hi Eric,
Works fine here, as you configured it.
Can you reply your inbound route-policy and the show route x.x.x.x/32
extensive?
Thanks.
Tim
On 26-04-13 15:36, Eric Krichbaum wrote:
This should be simple but I can't get the behavior I want.
Blackhole scenario. Customer set community, I want to see that community
and set next-hop to an address I have with a discard. I've tried both a
discard interface and a basic static route. Those seem ok either way.
set routing-options static route 192.0.2.1/32 discard
Route comes in and is accepted by policy. With no next-hop 192.0.2.1
action, I see it as a valid route so I know the policy is happening. When I
add the next-hop action, the route becomes "Next hop type: Unusable" with
"Inactive reason: Unusable path". I don't see anything special about this
and what I translated from my cisco versions doesn't look all that different
from various black hole presentations I find.
Anyone have a magic answer?
Thanks,
Eric
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
