[nsp] as-path prepend question

[Lucas Iglesias]

Hi,

I think the best way to do this kind of things is by using communities.
For example, you can set a community <MYAS>:<SRCNUM> where SRCNUM is the
number of the source originator number (if you have many of them) and then
prepend those prefixes on the exit routers based on these communities.
This should work fine, but of course, you have to have administration of the
source originator routers.

Regards,
Lucas.-


-----Mensaje original-----
De: Lukas Krattiger [mailto:luk at everyware.ch]
Enviado el: Martes, 09 de Septiembre de 2003 11:13 a.m.
Para: Gert Doering
CC: cisco-nsp at puck.nether.net
Asunto: Re: [nsp] as-path prepend question


Hi Gert

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

Best
-Lukas


At 15:27 09.09.2003, Gert Doering wrote:
>Hi,
>
>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 10.10.0.0 0.0.0.255
> > !
> > 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
>carefully.
>
>gert
>--
>USENET is *not* the non-clickable part of WWW!
> 
>//www.muc.de/~gert/
>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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/