from Hacker News

Show HN: Asroute – View unique networks traversed by traceroute

by steven_pack on 9/2/20, 3:38 AM with 17 comments

by dmytton on 9/2/20, 6:44 AM
Traceroute is fine for casual analysis but it is inaccurate and/or incomplete for anything serious because it misses routers that use load balancing on packet headers. For research purposes, it's better to use Paris Traceroute: https://paris-traceroute.net
> 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.

by jart on 9/2/20, 7:27 AM

If anyone's curious how the tool is obtaining this information:

    $ 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"

by jlgaddis on 9/2/20, 2:43 PM
Related: "Traceroute Lies! A Typical Misinterpretation Of Output" [0], previously discussed here on HN [1].
---
[0]: https://movingpackets.net/2017/10/06/misinterpreting-tracero...
[1]: https://news.ycombinator.com/item?id=15474043
by smnv on 9/2/20, 5:59 AM
mtr -z? I mean, it is a good learning effort, but if someone doesn’t know about mtr, they should: https://bitwizard.nl/mtr/
by samoa42 on 9/2/20, 7:31 AM
while the as_number->as_name lookup is usefull i would have opted for adding this feature to one (or more) of the existing utilities (traceroute, mtr, paris-traceroute) instead of crafting yet another command.