From: Jay Chandradas (jachandr@xxxxxxxxx)
Date: Thu Feb 01 2001 - 16:12:24 GMT-3
I think we can do a as path filer as well.
ip as path access-list 10 deny ^/as number for R1/$
ip as path acces-list 10 deny .*
inclide this as filer-list 10 in ur neighbor statement to R3.
Hope this helps
Jay.
----- Original Message -----
From: "Wade Edwards" <wade.edwards@powerupnetworks.com>
To: "Roy Grego" <ccsi100@yahoo.com>; <ccielab@groupstudy.com>
Sent: Thursday, February 01, 2001 9:58 AM
Subject: RE: 2 Questions 1 BGP, 1 DLSW backups
> >2) BGP filtering from
> > R1 (Network command) -- iBGP-- R2 --- EBGP -- R3
> >
> >Filter the route you injected in R1 from R3 not by IP.
> >
> >I was thinking TAG but on R2 it doesn't let you match
> >OUT based on a tag or Metric. When I tried route-type
> >internal it did work (well it blocked all the internal
> >routes).
> >
> >So I thought trying a community. I am not sure if I
> >configured the Network command properly to add a
> >community to that route.
> >
> >on R1
> >int loopback, ip addr 10.8.1.1 255.255.255.255
> >
> >router BGP 10
> > neighbor R2 send-community
> > network 10.8.1.1 mask 255.255.255.255 route-map TAG2
> >
> >route-map TAG2 p 10
> > set comm 1 no-export <-- Prevents from going to
> >other AS
>
> I believe you have to place the route-map on the neighbor statement like
> this.
>
> router BGP 10
> neighbor 1.1.1.1 remote-as 10
> neighbor 1.1.1.1 send-community
> neighbor 1.1.1.1 route-map TAG2 out
>
> route-map TAG2 permit 10
> match ip address 1
> set community no-export
>
> route-map TAG2 permit 20
> match ip address 2
>
> access-list 1 permit host 10.8.1.1
> access-list 2 permit any
>
> L8r
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:33 GMT-3