Hi,
I have a /32 that I'd like to redistribute via OSPF, the /32 is part of
a larger /24 that's directly connected to an interface of the router. I
don't want to advertise the whole /24 for various reasons, just the
route for the singe host.
Right now I have a static route:
static {
route 1.2.3.4/32 {
next-hop 1.2.3.4;
no-install;
}
}
That's then matched in a policy-statement that I use for export in ospf:
term static {
from {
protocol static;
route-filter 1.2.3.4/32 exact;
}
then {
external {
type 1;
}
accept;
}
}
This seems a little awkward (/32 static with a next-hop of itself) - is
there a cleaner way to do this?
Thanks for any tips!
--
matt
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
