On Thu, Oct 16, 2014 at 06:34:57PM +0200, Ondrej Zajicek wrote:
> Generally, the proper way is to identify mails from mailing lists by their
> List-ID header, which, as i checked now, is missing here and should be
> added.
Indeed, that would be really useful.
Thanks,
Baptiste
pgpCXZwydlzzz.pgp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.10.2014 14:06, Osmos wrote:
> Hi Ondrej,
>
> will need to join the way that IXPs do. What I get is AS_PATH not
> modified and next-hop modified.
>
> RS clients get next-hop attribute of route sever itself.
I see. That's wrong. Can you send me
Hi Ondrej,
will need to join the way that IXPs do.
What I get is AS_PATH not modified and next-hop modified.
RS clients get next-hop attribute of route sever itself.
Regards,
Jorge.
> El 22/10/2014, a las 17:58, Ondrej Filip escribió:
>
> -BEGIN PGP SIGNED MESSAGE-
>
Thanks Frederik,
is the intended behavior the one wanted to deploy.
Found that AS_PATH is not modified but next-hop is modified to RS itself.
Regards,
Jorge.
> El 22/10/2014, a las 15:20, Frederik Kriewitz escribió:
>
>> On Wed, Oct 22, 2014 at 2:56 PM, Osmos wrote:
>> Hi there,
>>
Hi John,
right, it makes sense.
After playing on lab, what I checked is that AS_PATH is not modified but
next-hop is pointing to route server itself.
Reading this draft, next-hop should be one of the rs client (depending on
prefix).
Configuration tested is based on eBGP session (i
