[j-nsp] BGP origination

[Hannes Gredler]

On Wed, Jan 29, 2003 at 08:10:37AM -0500, Richard A Steenbergen wrote:
| On Wed, Jan 29, 2003 at 12:33:49AM -0800, dre wrote:
| > Don't mix customer prefixes with your own infrastructure addressing.
| > Always save at least a few infrastructure addresses for customers,
| > namely the preferrably /31 (but is often /30 due to code limitations)
| > ptp links, and one loopback per customer (e.g. for bgp router-id per
| > neighbor).  keep N for gre, hsrp/vrrp, and other off-one situations
| > (plan accordingly; N is often larger with a smaller customer base).
| 
| You miss my point. Say a customer comes to you with their own /24, but
| they don't speak BGP (it happens). You have to announce it for them, and
| put it on an interface for them. If you want to use a static route for a 
| holddown, you're either gonna be putting it on the interface as 2 /25s, or 
| bust.

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 ...

/hannes