yvs2014

a possible fix of "ticking too fast" https://github.com/traviscross/mtr/commit/f89c17078deda0d3bd841cd515da4b79b0c2cada (it was for https://github.com/traviscross/mtr/issues/466, but probably that would be suitable in this case too)

Done, but I cannot create the second fork of the same repo. On copied branch it looks like below https://github.com/traviscross/mtr/compare/master...yvs2014:mtr085:mtr20230425-unspecaddr

Paraphrasing the question it's "Why paths to two or three different networks (142., 39., 110.) using two different protocols (udp and icmp) are different". The answer is in the Q...

If adding those options to display at runtime in future, I suppose both options and keyactions could be shown. Using a bit an older version with such displaying, can say,...

in some way it's probably similar to trace of some network or unspecified target ip address, if I'm not mistaken something like `mtr -n 0`

@PenelopeFudd > nearby routers throttle the TTL exceeded messages, and mtr starts showing "???" If that's only about to skip first nearby routers, filter '???' hops out, and leave unique...

> if the current hop has been seen before, the nearer hops will be identical What does it mean identical in this context? Possible identity (besides ip-address) could be ASN,...

> expecting it to be mostly static Just thought that the more general information, the more static it is and less likely to be changed. Like for the path above:...

@PenelopeFudd > when you're mapping a network that that doesn't use multi-path protocols > not sure which interface routers might report in traceroute (or mtr) shows ip-addresses of routers from...

I've tried to add some cache mode inside mtr (to older version so far) with the next algorithm: if n-th hop is 'up' and seen less than 'cache-timeout' period, then...