Yes, I like that idea too.. thanks for sharing that...;) Paul
-----Original Message----- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Chuck Anderson Sent: January-12-11 7:23 PM To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Aggregate Routes Revisited On Wed, Jan 12, 2011 at 04:01:45PM -0500, Paul Stewart wrote: > Just wanted to write back to the list and say THANK YOU! I had already > created a policy very similar to what you had suggested - but - when I added > it to the outbound policy for the upstream I didn't pay attention to the > order it was applied. I've generally taken to having a separate REJECT policy that simply does "then reject" and I use it at the end of a policy chain instead of hardcoding a "then reject" term in any other policy. policy-statement REJECT { term REJECT { then reject; } } export [ TO-FOO MATCH-BAR REJECT ]; _______________________________________________ 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