From: John White (jan_white7@xxxxxxxxxxx)
Date: Tue Jul 09 2002 - 02:15:01 GMT-3
After doing some research, it seems to me that probably most elegant way
of doing this would be marking packets with community on ingress and
filtering them on egress
The most simple way though , would be just allowing only internal networks
out.
Thank you guys
Jan
>From: "Nick Shah" <nshah@connect.com.au>
>Reply-To: "Nick Shah" <nshah@connect.com.au>
>To: "John White" <jan_white7@hotmail.com>, <ccielab@groupstudy.com>
>Subject: Re: As Transit
>Date: Tue, 9 Jul 2002 14:43:02 +1000
>
>There are a more than couple of ways to do this... I will quote one
>
>Say RtrA (AS1)---- RtrB (AS2)----- RtrC(AS3)
>
>You dont want RtrB to be a transit AS for prefixes advertised from RtrA,
>essentially send prefixes from RtrA with a no-export Community.
>
>Basic idea is *not advertising* RtrA's prefixes to RtrC (and the other way
>around), so you can sure find more than this way to acheive this. (Let me
>know if you have any difficulty)
>
>rgds
>Nick
>----- Original Message -----
>From: "John White" <jan_white7@hotmail.com>
>To: <ccielab@groupstudy.com>
>Sent: Tuesday, July 09, 2002 1:59 PM
>Subject: As Transit
>
>
> > 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?
> > Thanks.
> > Jan
> >
> >
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:23 GMT-3