From: Sage Vadi (sagevadi@yahoo.co.uk)
Date: Sun Jan 12 2003 - 20:42:47 GMT-3
Gustavo,
This is my understanding of your problem: you want the
40.40.40.0 to die IN AS254.
I'm assuming you have admin control of R2. This is
what we shall do: on R2 we tell R5 to not-advertise
40.40.40.0 route outside the AS254 AS or to
not-REadvertise the route @ all.
As Nate suggested we can do these with communities.
NO_EXPORT (don't send outside this AS) and
NO_ADVERTISE (don't reAdvertise @ all).
Try this on R2:
router bgp x
~
neighbor R4 send-community <--- MANDATORY
neighbor R4 route-map xxx out <-- route_map
ip access-list standard yyy <-- ACL named yyy
permit 40.40.40.n <-- permit these networks
route-map xxx permit 10
match ip address yyy
set community no-export no-advertise <-- (depending on
what you want to do)
route-map send-community permit 11 <-- permit all
OTHER networks
Try this and let me know you go.
For more info about BGP communities please check:
(watch wordwrap).
Cheers,
Sage
--- Gustavo Figueira <gufigueira@ig.com.br> wrote: >
Hi group,
>
> I have the following topology:
>
>
>
R4-----ibgp-----R1------ebgp------R2--------ebgp-----R5
>
>
> R4 and R1 are in the AS19
> R2 are in the AS65019 and
> R5 are in the AS254
>
> I am announcing loopback 40.40.40.4 in the R4. R5
> has the net in its table
> BGP, however, can't announces it. The network
> 40.40.40.0 has that to die in
> the AS254. How I make this?
>
> I don't have access to the R5.
>
> Thank's
>
> Gustavo
> .
>
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:47 GMT-3