Re: Reverse Traceroute

Before "revtr-lg" sticks, in the grand tradition of Paris Traceroute and Tokyo Ping we call our version of traceroute "Augsburg Traceroute". And it does not resemble a looking glass server. There are two parties involved in a reverse traceroute operation (not counting the routers that reply to

Re: BGP Engines with support to "RTFilter address-family"

Hello, On Sun, 26 Feb 2023 17:46:42 -0300 Douglas Fischer wrote: > But I'm looking for an open-source engine that supports it. > > The official FRR documentation does not mention anything about RFC 4364, > or RTFilter address family. > So, I think FRR does not support RTFilter Constrained

Re: Reverse Traceroute

Chris, thanks for mentioning me/our project! Rolf, thanks for pointing to our recent 2nd reverse traceroute paper ! Our recent paper addressed what we saw as the major limitations of my original 1st reverse traceroute paper

Re: Reverse Traceroute

On 2/25/23 3:09 AM, Tore Anderson wrote: I suggest you get in touch with the fine folks at NLNOG RING and ask it they would be interested in setting this up on the 600+ RING nodes all over the world. See https://ring.nlnog.net/. Similarly you might reach out to RIPE and inquire if they are

BGP Engines with support to "RTFilter address-family"

We are implementing an interesting L3VPN scenario for distributed DFZ on mid-size PEs. And we believe that the RT Constrained Route Distribution, RFC4684, will be ideal to solve the problems of operational levels for the intervention of configurations between PEs and Route-Reflectors. However,