[nsp] as-path prepend question

Pete Templin pete.templin at texlink.com
Tue Sep 9 11:11:10 EDT 2003

You'll probably want to continue announcing your aggregate as you are, and then add a more-specific announcement to which you'll prepend as desired.

Pete Templin
Senior Staff Engineer
TexLink Communications
(210) 892-4183
pete.templin at texlink.com

-----Original Message-----
From: Lukas Krattiger [mailto:luk at everyware.ch]
Sent: Tuesday, September 09, 2003 9:13 AM
To: Gert Doering
Cc: cisco-nsp at puck.nether.net
Subject: Re: [nsp] as-path prepend question

Hi Gert

That's what I find out too ... did anyone has a suggestion ?


At 15:27 09.09.2003, Gert Doering wrote:
>On Tue, Sep 02, 2003 at 11:09:53AM +0200, Lukas Krattiger wrote:
> > I want to prepend a path based on the source ip with two additional hops
> > and the rest with one, here the config-part as I understand
> > !
> > access-list 1
> > !
> > route-map ASprepend-OUT permit 10
> >   match ip address 1
> >   set as-path prepend <MYAS> <MYAS>
>I think this won't work, as "match ip address" in BGP route-maps tends
>to match the *prefix*, and not the originating router.  So watch this
>USENET is *not* the non-clickable part of WWW!
>Gert Doering - Munich, Germany                             gert at greenie.muc.de
>fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de

cisco-nsp mailing list  cisco-nsp at puck.nether.net
archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list