[j-nsp] BGP origination

[Clayton Fiske]

On Wed, Jan 29, 2003 at 11:22:29AM -0500, Richard A Steenbergen wrote:
> On Wed, Jan 29, 2003 at 02:50:37PM +0100, Hannes Gredler wrote:
> > 
> > why relying on a static route if we have a direct route ?
> > 
> > policy-options {
> >     policy-statement adv-customer-xyz {
> >        from {
> >            protocol direct;
> >            route-filter 192.168.1.0/24;
> >        }
> >        then accept;
> >    }
> > }
> > protocols {
> >     bgp {
> >         group to-my-upstream {
> >             export adv-customer-xyz;
> >         }
> >     }
> > }
> > 
> > should do the trick ...
> 
> Because then I lose the ability to easily tag that /24 with communities, 
> as-path, etc, as I would when defining a static holddown route. At best, I 
> end up with a REALLY ugly policy-statement to do it.

What is the "non-ugly" way you would use with a static route? For the
(admittedly few) static routes we pull into BGP, our policies are not
unlike the example above (s/direct/static/). We just use the 'then'
section to set attributes.

-c