From: Nick Shah (nshah@xxxxxxxxxxxxxx)
Date: Tue Jul 09 2002 - 21:04:07 GMT-3
This is a *perfect* answer in a production world.
But in a controlled/lab environment, where mostly one router belongs to one
AS, it may not be practically possible. That leaves only prefix filtering by
no-community and/or all forms of prefix filters (distribute lists etc.)
rgds
Nick
Message -----
From: "Tom Larus" <tlarus@cox.net>
To: "Jay Hennigan" <jay@west.net>; "John White" <jan_white7@hotmail.com>
Cc: <ccielab@groupstudy.com>
Sent: Wednesday, July 10, 2002 12:13 AM
Subject: Re: As Transit
> This is probably not what they are looking for, but if you leave synch on,
> and do not redistribute bgp routes into you igp, you will definitely NOT
> become a transit AS.
>
> Is the real answer to set all your incoming bgp routes to no-export?
>
> ---- Original Message -----
> From: "Jay Hennigan" <jay@west.net>
> To: "John White" <jan_white7@hotmail.com>
> Cc: <ccielab@groupstudy.com>
> Sent: Tuesday, July 09, 2002 12:39 AM
> Subject: Re: As Transit
>
>
> > On Tue, 9 Jul 2002, John White wrote:
> >
> > > Hi Guys,
> > > I'm doing Cisco Aset lab.One of question is to prevent our AS from
> becoming
> > > Transit AS, but your not allowed to use AS path filtering.
> > > Learning routes from outside shuould be still possible.
> > > Somehow I can't think of anything else. Distribution list?Community
> list?
> >
> > Hint:
> >
> > Look at the well-known community attributes.
> >
> > --
> > Jay Hennigan - CCIE #7880 - Network Administration - jay@west.net
> > NetLojix Communications, Inc. - http://www.netlojix.com/
> > WestNet: Connecting you to the planet. 805 884-6323
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:24 GMT-3