3 ms·
I did this a few years ago, a simple tool that pinged places all over the world and calculated where you should be. This only ever gets as close as your ISP, o
by lucb1e 10y ago
I did this a few years ago, a simple tool that pinged places all over the world and calculated where you should be.
This only ever gets as close as your ISP, or perhaps a local routing center if your ISP has multiple (mine has only one in Amsterdam, I live on the other side of the country). This means it's less accurate than your typical GeoIP database.
Edit: I'm no longer sure this is the same. The title mentions "passive", and from another comment I understand that the author meant that you can find someone's location if you are the man in the middle, observing traffic to various places around the world. This is definitely something I had not considered yet!
- coroutines 10y agoI'm thinking this might become pretty important with IPv6, no? My ISP advertises a prefix I can do SLAAC with, but they won't allow you to assign an arbitrary address outside that prefix (which seems reasonable-ish for routing). GeoIP databases will have a harder time with IPv6, but if ISPs only use prefixes like this then it'll still be manageable..
- chias 10y agoIt isn't passive. See lines 64-73 of the code [1]. This seems very similar to what you describe, but rather than you pinging a bunch of places around the world, it has a bunch of places around the world essentially pinging you. If you check the HTML source, it's src'ing scripts from machines around the world (I assume whatever host is being used, the author has spun up a VPN in each of their data centers). Here's an example of one [2]. Each of these sends you a constant value over and over again, and the server side measures the latency, before finally reporting the average round-trip time to you. [1]: http://geoloc.foremski.pl/tcpinfo.go http://geoloc.foremski.pl/tcpinfo.go [2]: http://46.101.226.53/DE_Frankfurt.js http://46.101.226.53/DE_Frankfurt.js