[HN Gopher] Show HN: Traceroute Visualizer
___________________________________________________________________
Show HN: Traceroute Visualizer
This nifty tool plots the traceroute results and shows you the RTT
as well as the distance travelled by the packets! Supports MTR,
flyingroutes and of course, traceroute. The existing solutions
were too limited so I made that. Let me know if you have any
feedback
Author : PranaFlux
Score : 44 points
Date : 2025-09-29 08:31 UTC (3 days ago)
(HTM) web link (kriztalz.sh)
(TXT) w3m dump (kriztalz.sh)
| don_searchcraft wrote:
| This is pretty sweet, nice job. i dig the mapping visualization.
| Meph504 wrote:
| I'm not sure if this worked as intended when tracert to
| google.com I get my IP, skips 13 hops, then 10 unknowns?
| OlivOnTech wrote:
| I'm on my phone, maybe your site would benefit having sample data
| available to showcase what it can do?
| Lalo-ATX wrote:
| didn't work for me at all.
|
| auto-detected my IPv4 addy, but my tracert to google.com went
| over IPv6.
|
| I'm pretty skeptical about being able to geolocate router
| interfaces from IP addresses, so I was curious about the output.
| My expectations were low but they were too high. Oh well.
| observationist wrote:
| In principle, if you ping from multiple known interfaces and
| paths, you can infer probable location, with confidence going
| up with the more known points of reference you have. You can do
| a little calculation and triangulation based off of latency and
| responsive known targets traversing the same path as the
| endpoint you're trying to geolocate, and get a very high
| confidence result for zip code, city, or maybe even 3-4 block
| radius, if there are a bunch of ISPs in the region. Even with
| only 3-4 ISPs, by sourcing from different directions along
| different networks you can get more resolution in the final
| estimated radius for geolocation.
|
| You can even use a whole bunch of fuzzy rough estimations for
| endpoints in a region to get progressive increments in
| resolution until you're happy with a precise location. You can
| also use educated guesses about the type of router at each hop,
| then use response times and behaviors for pings coming from
| different directions at different times. If you can arrange to
| traverse a node and pump traffic over it, you can use behavior
| with different types of traffic to elicit the type of router,
| the policies in place, and so on.
|
| It's a good idea to turn off responses to pings and minimize
| the amount of information available, even if it seems mostly
| harmless. The amount of information you can get from the public
| internet, just in terms of basic network utility functions and
| behaviors, is probably a lot more than most people ever
| consider.
| kam wrote:
| The calls to the ipinfo.io API are blocked by Firefox Enhanced
| Tracking Protection. No results for Location or ISP without
| turning that off.
| observationist wrote:
| The site is flagged as "phishing" by Palo Alto - submitted
| change request.
|
| edit: They updated from phishing to "computer and internet
| info" , no longer blocked.
| tonymet wrote:
| I love more tooling and attention given to latency . Throughput
| gets the attention but latency is what drives a high quality
| experience
| bpbp-mango wrote:
| I don't think it works with Windows tracert output
|
| edit: edited my windows traceroute to match the linux format and
| it works nicely. great tool.
___________________________________________________________________
(page generated 2025-10-02 23:00 UTC)