Traceroute is becoming more and more an expert's tool because interpretation of its results isn't straightforward. I had written a paper last year and mentioned its misuse in academia in the context of estimating the number of energy-consuming devices between a source and a destination. Traceroute was being used to count the number of physical router devices from the hop count, notwithstanding the use of MPLS in domain cores. To an external observer, this results in significant underestimation of the energy consumption in the path from source to destination. On Thu, Dec 12, 2019 at 12:51 AM Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
On Wed, 11 Dec 2019 19:26:09 +0200, Saku Ytti said:
On Wed, 11 Dec 2019 at 19:14, Rob Foehl <rwf@loonybin.net> wrote:
Support claims that it was a mistake, but it's also been 15+ months and it's pretty deliberate behavior. Draw your own conclusions...
TTL decrement issues are fairly common across multiple vendors and hw, can be sw can be hw limit
Yes, but you need to screw up gloriously on the decrement if you think that "I decremented and it's zero now" means "therefor it must have been addressed to me, so I'll send an ECHO REPLY instead of TTL EXCEEDED".
-- Ing. Etienne-Victor Depasquale Assistant Lecturer Department of Communications & Computer Engineering Faculty of Information & Communication Technology University of Malta Web. https://www.um.edu.mt/profile/etiennedepasquale