> Why should you use Paris traceroute?
> Because traceroute fails in the presence of routers that employ load balancing on packet header fields. The failures lead to the discovery of inaccurate and incomplete paths, that may mislead operators during problem diagnosis and result in erroneous internet maps. Paris traceroute, by controling packet header contents, obtains a more precise picture of the actual routes that packets follow.
> Dublin Traceroute uses the techniques invented by the authors of Paris-traceroute to enumerate the paths of ECMP flow-based load balancing, but introduces a new technique for NAT detection.
---
[0]: https://github.com/insomniacslk/python-dublin-traceroute
$ dig +short TXT 8.8.8.8.origin.asn.cymru.com
"15169 | 8.8.8.0/24 | US | arin | 1992-12-01"
$ dig +short TXT AS15169.asn.cymru.com
"15169 | US | arin | 2000-03-30 | GOOGLE, US"
See also https://team-cymru.com/community-services/ip-asn-mapping/#dn...---
[0]: https://movingpackets.net/2017/10/06/misinterpreting-tracero...
-z, --aslookup
MISSING
I assume from the context that it does the mtr equiv "traceroute -A" though $ traceroute -A ...
$ mtr -z ...