From: Brian McGahan (brian@cyscoexpert.com)
Date: Mon Sep 16 2002 - 12:35:48 GMT-3
Harbir,
Are you sure you know what you're trying to accomplish here? If
you want to prevent your AS from being transit, all you have to do is
advertise an empty AS set out. It doesn't matter if you are part of a
confederation because from your EBGP neighbor's perspective, you are
only a single AS. Your EBGP peers know nothing about your internal
routing policy, which includes any confederation setup you have.
HTH
Brian McGahan, CCIE #8593
Director of Design and Implementation
brian@cyscoexpert.com
CyscoExpert Corporation
Internetwork Consulting & Training
http://www.cyscoexpert.com
Voice: 847.674.3392
Fax: 847.674.2625
> -----Original Message-----
> From: CCIE FUN [mailto:ccieexam2002@yahoo.com]
> Sent: Monday, September 16, 2002 9:42 AM
> To: Kohli, Harbir; 'ccielab@groupstudy.com'
> Cc: 'Brian McGahan'
> Subject: RE: BGP
>
> Possibly,
> you could setup some kind of filter list. which will
> "only " announce networks from the Confeds to the two
> other AS's.
> Make sure, your AS only advertises its own network to
> the respective neighbor AS's
>
>
>
>
>
> --- "Kohli, Harbir" <harbir.kohli@bellnexxia.com>
> wrote:
> > HI,
> > How do you make sure that your AS is not used as a
> > transit AS when your AS
> > is a confed of 6, 250, 8.
> >
> > From Halabi's book I though all you had to do was
> > Ip as-path access-list 1 permit ^$
> >
> > Router bgp x
> > Neighbor a.b.c.d filter-list 1 out
> > End
> >
> > But this does not work when using confederations.
> >
> > What would be the simplest solution?
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! News - Today's headlines
> http://news.yahoo.com
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:53 GMT-3