From: Earl Aboytes (earl@xxxxxxxxxxxx)
Date: Fri Jul 21 2000 - 23:07:03 GMT-3
I think that the answer you are looking for would be to filter based on the
as-path. Lets say that this network was one of many that originated in AS
11. You could use an as-path access-list that filtered all that originated
from that AS.
For example:
ip as-path access-list 1 deny _11$
route-map as11filter deny 10
match as-path 1
!
route-map asfilter11 permit 20
router bgp 20
neighbor 138.51.35.1 remote-as 22
neighbor 138.50.1.1 route-map asfilter11 out
I threw this together fairly quickly. Please verify this with Halabi's
book.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Earl Aboytes
Senior Technical Conultant
GTE Managed Solutions
805-381-8817
earl.aboytes@telops.gte.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Mike
Hess
Sent: Friday, July 21, 2000 6:34 PM
To: ccielab@groupstudy.com
Subject: RE: BGP Filtering
You could filter on the subnet length (I know, this is kind of like ip
address)
For instance, say you only wanted to accept routes with 24 bit subnet masks:
route-map infilter permit 10
match ip address 100
access-list 100 permit ip an host 255.255.255.0
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Bob Woodson
> Sent: Friday, July 21, 2000 1:18 PM
> To: ccielab@groupstudy.com
> Subject: BGP Filtering
>
>
> What other methods of bgp filtering are available to
> filter a route to or from an EBGP peer "other than by
> ip address"? Let's say I wanted to filter the route
> to or from 139.50.5.0/24. Can anybody provide any
> examples?
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:57 GMT-3