And you have right. But since there was no other public possibility, the no-export won! It was kinda Brain-storming.. sorry for
that.. I wanted to know if there is any other possibility..since there isn't no-export had to win!
many thanx
alex
-----Original Message-----
From: Philip Smith [mailto:pfs@cisco.com]
Sent: Friday, January 11, 2002 1:31 PM
To: kf@reign.sk
Cc: cisco-nsp@puck.nether.net
Subject: RE: [nsp] BGP TRICK
No-export is a community. You said no communities.
philip
--At 13:12 11/01/2002 +0100, KF wrote: >yup, no-export is the right answer... many thanks for Brain-Storming ;-)) > >greetz > >Alex > >-----Original Message----- >From: Ryan O'Connell [mailto:ryan@complicity.co.uk] >Sent: Friday, January 11, 2002 12:44 PM >To: KF >Cc: 'Brian Wallingford'; cisco-nsp@puck.nether.net >Subject: Re: [nsp] BGP TRICK > > >On Fri, Jan 11, 2002 at 12:24:11PM +0100, KF wrote: > > no-no...surely not. idea is how to annouce local network ONLY to the > next AS, without any REMOTE filtering. So the annouced >network > > stays within the nex AS , but never cross it.. There is ONLY one > speaker so AS prepending is NOT possible..nor communities.. > >I assume basically you're trying to announce something to a remote AS but >you don't want them to propagate that AS? If you can't use communities at >all, even standard ones like no-export/local-as then BGP won't do that for >you. > >If you actually just want the remote AS to use a direct link for traffic but >the rest of the 'net use another link, AS-path prepending may work - many ISPs >set higher preferences on customer advertisments and will use that in >preference to a peer/exchange point link regardless of AS-path length. > >-- > Ryan O'Connell - CCIE #8174 ><ryan@complicity.co.uk> - http://www.complicity.co.uk > > >I'm not losing my mind, no I'm not changing my lines, >I'm just learning new things with the passage of time
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:28 EDT