Thanks everyone. The policy straight to discard works for me, just annoyed me. I really didn't want to apply a knob (similar to the disable connected check on cisco) to do it. Trying to make these policies the same has proven an interesting exercise and at least now I am aware of the knobs to make it do the other.
Eric -----Original Message----- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of David Waldman Sent: Friday, April 26, 2013 10:59 AM To: Tim Vollebregt Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] next-hop driving me crazy Eric. eBGP single hop will not let you change the NH by default. You can use the following knob to override this behavior: protocols { bgp { log-updown; group TRIGGER { accept-remote-nexthop; This can be applied @ proto group or neighbor. See http://www.juniper.net/techpubs/software/junos/junos94/swconfig-routing/acce pt-remote-nexthop.html for more info. Regards. david On Fri, Apr 26, 2013 at 10:35 AM, Tim Vollebregt <t...@interworx.nl> wrote: > 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<https://puck.n >> ether.net/mailman/listinfo/juniper-nsp> >> > > ______________________________**_________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/**mailman/listinfo/juniper-nsp<https://puck.ne > ther.net/mailman/listinfo/juniper-nsp> > _______________________________________________ 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