rolf.winter at hs-augsburg.de
Wed Feb 22 18:19:42 UTC 2023
I cannot/shouldn't really answer, since this is somebody else's work.
The latest publication on that body of work can be found here:
Published at IMC 22 last October.
I believe a demo is actually online here: https://revtr.ccs.neu.edu/
That piece of work and ours differ in a number of ways. Whereas the work
you cite is an external system really, that let's you perform a reverse
traceroute through said system, we have implemented something, that
works just like traceroute does today, but for the reverse direction.
I.e. it works from your terminal, performing a traceroute back to you.
The system you mention has an accuracy of about 92% at the AS-level.
Since we perform the actual measurement between two endpoints we
identify the actual forwarding path, at the router-level, including
But we use ICMP and would need code points to move forward. So if you
find this useful, discussion on the IntArea mailing list would be
Am 22.02.23 um 18:19 schrieb Christopher Morrow:
> Didn't ethan's project:
> end with usable code/etc?
> On Wed, Feb 22, 2023 at 8:09 AM Rolf Winter <rolf.winter at hs-augsburg.de> wrote:
>> Dear NANOG folks,
>> As you know, traceroute is unable to enumerate routers on the reverse
>> path. Given that paths through the public internet are usually
>> asymmetric, knowing the reverse path would be beneficial e.g. for
>> troubleshooting purposes (https://youtu.be/L0RUI5kHzEQ?t=2312).
>> We have implemented a reverse traceroute tool
>> (https://github.com/hsanet/reverse-traceroute), both client and server
>> for both IPv4 and IPv6. We are also in the process of specifying the
>> protocol at the IETF
>> We also gave a talk on reverse traceroute at DENOG14
>> If you would like to play with reverse traceroute, the easiest option is
>> to work with the client and use one of the public server instances
>> (https://github.com/HSAnet/reverse-traceroute/blob/main/ENDPOINTS). If
>> you would be willing to host a public server instance yourself, please
>> reach out to us. Also, if you find this work useful, please start
>> discussing the work at the IntArea WG at the IETF.
>> If you have any questions or comments, just drop us a line, file an
>> issue on github and/or use the IntArea mailing list.
>> Thanks a bunch,
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4757 bytes
Desc: S/MIME Cryptographic Signature
More information about the NANOG