We have ipinfo at home or how to geolocate IPs in your CLI using latency
blog.globalping.io
We have ipinfo at home or how to geolocate IPs in your CLI using latency
1–10 of 65 posts
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#2This is a little project exploring the feasibility of using a service such as Globalping for geo location needs.
I had fun making it but please note that the current implementation is just a demo and far from a proper production tool.
If you really want to use it then for best possible results you need at least 500 probes per phase.
It could be optimized fairly easily but not without going over the anon user limit which I tried to avoid
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#3Bit surprised this works. Latency variability is huge and sometimes quite disconnected from geo location. I recall talking to someone in NL and realised I've got better latency to NL content from the UK than he did. Presumably better peering etc.
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#4How feasible would it be for the host under measurement to introduce additional artificial latency to ping responses, varying based on source IP, in order to spoof its measured location?
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#5How feasible would it be for the host under measurement to introduce additional artificial latency to ping responses, varying based on source IP, in order to spoof its measured location?
Totally feasible but a bit like all these situations - it’s not happening in practice.
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#6How feasible would it be for the host under measurement to introduce additional artificial latency to ping responses, varying based on source IP, in order to spoof its measured location?
Not-impossible, but it would be a whole lot simpler to just not respond to pings in the first place.
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#7How feasible would it be for the host under measurement to introduce additional artificial latency to ping responses, varying based on source IP, in order to spoof its measured location?
Totally feasible.
You could do even cooler tricks, like https://github.com/blechschmidt/fakeroute
Pointless? Almost certainly.
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#8Wow, it works !
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#9How feasible would it be for the host under measurement to introduce additional artificial latency to ping responses, varying based on source IP, in order to spoof its measured location?
Courtesy of Xfinity and Charter overprovisioning most neighborhood’s circuits, we already have that today for a significant subset of U.S. Internet users due to the resulting Bufferbloat (up to 2500ms on a 1000/30 connection!)
Re: We have ipinfo at home or how to geolocate IPs in your CLI using latency
#10Amazing idea and execution, the sort of stuff I wish there was more of on HN.