←back to thread

Trippy – A Network Diagnostic Tool

(trippy.cli.rs)
265 points night-rider | 2 comments | 10 Dec 23 03:46 UTC | HN request time: 0.673s | source
Show context
bastard_op ◴[10 Dec 23 06:49 UTC] No.38589668[source]▶
As a network engineer, it's a neat tool, I installed it on arch, and had the mmdb to point at for geo, so that was cool, but mostly unrealistic. My customer in nyc from phoenix says goes via switzerland, but at least I know better. I sent out to my current customers slack channel to check out, it's at least prettier than mtr.
replies(1): >>38589718 #
FujiApple ◴[10 Dec 23 07:02 UTC] No.38589718[source]▶
Yes, in my experience GeoIp is _highly_ unreliable, alas Trippy can do no more than report the location from the provided mmdb file.

I'm aware of some interesting techniques which use timing measurements from multiple locations to try and triangulate a more accurate location. In fact somebody raised a request for supporting JA4L [0] to me just this morning.

[0] https://github.com/fujiapple852/trippy/issues/856

replies(2): >>38590943 #>>38591595 #
1. mrngm ◴[10 Dec 23 14:09 UTC] No.38591595[source]▶
You might also be interested in "geofeed" attributes in the WHOIS databases, in some database they can be found in a "remarks" field).

This record usually leads to an RFC 8805 formatted document that shows a mapping between IP address ranges and their (approximate) location. In RFC 9092, efforts were made to make this a more structural field.

replies(1): >>38591702 #
2. FujiApple ◴[10 Dec 23 14:28 UTC] No.38591702[source]▶
Thank you, I'll look into those RFCs.