Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.protocols.tcp-ip    |    TCP and IP network protocols.    |    14,669 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 14,438 of 14,669    |
|    Karl Kleinpaste to groovee@cyberdude.com    |
|    Re: How does geolocation work?    |
|    27 Mar 20 12:05:55    |
      From: karl@kleinpaste.org              On 3/27/20 6:34 AM, groovee@cyberdude.com wrote:       > How does this actually Work              There exist databases from allocation of addresses to service providers       which include the geographic coverage of the allocated address blocks.       My Linux systems have a package named GeoIP-GeoLite-data installed,       containing these databases. As well, there are command line tools in       GeoIP and C APIs available in GeoIP-devel.              Oftentimes, the result is quite wrong. I get 90+% of my Internet access       via AT&T hotspots. AT&T uses CGN (carrier-grade NAT), one effect of       which is that my apparent address as seen across the Internet depends on       where my connections through AT&T exit the AT&T network into other       providers. As a result, web searching for "what is my ip address" gives       me links to sites that are happy to tell me all about myself, among       which are their guesses for location; at the moment, depending on which       guess I read, they think I'm in either the Bronx, NYC, NY or Hartford,       CT. I'm actually northeast of Pittsburgh.              VPNs destroy geolocation. When I am traveling and using a VPS I rent,       running a VPN hub, the appearance is that I'm in Dallas. I haven't been       physically in Dallas in decades.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca