Skip to content

Comment on MTR: 'traceroute' and 'ping' in a single toolparent

Comments

Somewhere in another thread I retracted my issue with the ICMP handling code. But you've nailed my #1 gripe, the per-hop loss indicator is testing control path for diagnostic packets at each hop when the tool is meant to diagnose end to end latency and loss. How do you square a router or many routers showing packet loss when there's 0% end to end loss; it doesn't make sense, it's unintuitive, and that's how misleading inferences manifest.

Whatever the 80% lost packets on the router and next hop mean, there is either a serious problem with the tool or with my router AND the next hop.

I will go for the tool because it is the only one that warns about such a problem.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.