From: Padhu (LFG) (padhu@xxxxxxxxxxxx)
Date: Sun Jul 01 2001 - 02:12:02 GMT-3
I think there is a catch here ! if the local AS is made of confederations,
then these routes will not be available even in the confed peers within the
AS.
No - export would be clean.
Cheers,Padhu
-----Original Message-----
From: Darren Ward
To: Kris Foster
Cc: Malik Annur; Group Study
Sent: 6/29/01 9:34 PM
Subject: Re: BGP: Non-transit AS: Let me count the ways...
Another way:
Assign the community Local-AS to all incoming NLRI's and use the
neighbor send-community to distribute
the community information.
This ensures routes will not be advertised to any other AS.
Darren
Kris Foster wrote:
> Few ways off the top of my head:
>
> - Filter ebgp updates (out) to allow only ^$
> - Set the no-export community (or one of your own and match on the way
> out)
> - Use a distribute list to allow only your networks
> - Filter _all_ incoming updates so you don't recieve anything external
in
> your AS.
>
> Probably some other tricky ways but they're not coming to mind,
>
> Kris,
>
> On Tue, 26 Jun 2001, Malik Annur wrote:
>
> > How many ways can I force my AS100 to be a non-transit AS? I'm
trying to
> > assess all of my options.
> >
> > TIA
> >
> > Mal
> >
> > [GroupStudy.com removed an attachment of type application/ms-tnef
which had a name of winmail.dat]
> > **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:28 GMT-3