From: Paul (p_chopin@xxxxxxxxx)
Date: Mon May 27 2002 - 14:31:02 GMT-3
Yes, this would do it .But.. the only form of this
command I found is distance bgp external internal
local
It doesn't have <acl> option.So in this case all
external networks coming to peer wont' be installed
Paul
--- Carlos G Mendioroz <tron@huapi.ba.ar> wrote:
> Here!
> You can force an admin distance to routes learned
> from a bgp neighbour
> using router bgp <as>/ distance <d> <source> <mask>
> <acl>
>
> If you force admin distance to 255, the route will
> be IGNORED.
> (i.e. it will not go to the route table)
> It will be in the bgp table though, so your
> aggregate will be
> constructed and it will show in the route table.
>
> I guess this one makes it...
>
> Paul wrote:
> >
> > Hi guy,
> > Here it is scenario. R1 is getting external routes
> > from other AS. R1 is doing aggregation and sending
> > only aggregate towards internal peers. Question is
> how
> > to prevent R1 from installing specific routes into
> its
> > own routing table.It should have only aggregate.
> > Paul
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:10 GMT-3