Show HN: Improved passive TCP/IP geolocation
sheerun.gitlab.io
Show HN: Improved passive TCP/IP geolocation
1–10 of 43 posts
Re: Show HN: Improved passive TCP/IP geolocation
#2Can I assume this was meant to show my own location?
If so, I can assure you I'm not in India, Pakistan or Oman (or the middle of the Indian Ocean) as it suggested.
Re: Show HN: Improved passive TCP/IP geolocation
#3Can I assume this was meant to show my own location? If so, I can assure you I'm not in India, Pakistan or Oman (or the middle of the Indian Ocean) as it suggested.
I have to agree with this. I'm pretty sure that the middle of the Atlantic Ocean isn't quite the same as the U.S. East Coast...
Re: Show HN: Improved passive TCP/IP geolocation
#4Feels a bit overconfident - it was much better than the previous approach, and it got better over the iterations, getting very close - but however, 100% of the time my actual location was outside the circle.
I.e., the center points seem reasonable, but the size of circle is unreasonably small because it's obviously smaller than your actual precision.
Re: Show HN: Improved passive TCP/IP geolocation
#5The ping class likely needs to be scrapped to make this any sort of reliable.
Making a fake image request to these servers introduces a lot of very random sources of latency over what a typical ping would involve.
Re: Show HN: Improved passive TCP/IP geolocation
#6The ping class likely needs to be scrapped to make this any sort of reliable. Making a fake image request to these servers introduces a lot of very random sources of latency over what a typical ping would involve.
The other website posted on HN yesterday was much more accurate in that it had very large error circle and I was within the circle. This one tries to be way to specific which you simply can't do with this technique.
Re: Show HN: Improved passive TCP/IP geolocation
#7The ping class likely needs to be scrapped to make this any sort of reliable. Making a fake image request to these servers introduces a lot of very random sources of latency over what a typical ping would involve.
The other website posted on HN yesterday was much more accurate in that it had very large error circle and I was within the circle. This one tries to be way to specific which you simply can't do with this technique.
It could be "Improved Improved" if they had a central server constantly polling the nodes in exactly the same fashion as this script does. If you know the distance from your central server to the nodes, you can use the rolling response times you're polling for to establish a baseline for the client to help factor out server load.
Re: Show HN: Improved passive TCP/IP geolocation
#8This has apparently actually identified my antipode.
I also feel like circling entire continents doesn't count...
Re: Show HN: Improved passive TCP/IP geolocation
#9I tried with my real IP, and then again tunneled through a VPN 3 times each to different continents and it got all four 100% correct.
The VPN tests did have lower confidence, IE larger zones, but my end point was indeed in the circle. Pretty neat.
Re: Show HN: Improved passive TCP/IP geolocation
#10I can say for sure I am not in Chicago. But at least it got the right country. Incidentally at one point it circled almost my exactly location and then proceeded to walk elsewhere.
Update: I tried a second time. The second time it actually nailed my location pretty closely. The circle actually enclosed the state I'm actually in. The third time it was off again but at least close than the first.