From @Azulan on Mon Jan 18 2016 08:26:08 GMT+0000 (UTC)
How can I configure the node to share what City or Country I’m in?
Copied from original issue: https://github.com/ipfs/faq/issues/91
From @lidel on Mon Jan 18 2016 09:41:00 GMT+0000 (UTC)
These values are tied to the IP you use:
Example: http://freegeoip.net/json/8.8.8.8
From @meulie on Sun Mar 27 2016 13:49:51 GMT+0000 (UTC)
But what if this info is incorrect/inaccurate? Is there a way to tune this?
From @lidel on Sun Mar 27 2016 15:34:35 GMT+0000 (UTC)
I think you need to find out which data provider manages your IP range and contact them directly.
As far I know update may take from a few weeks to months.
From @RichardLitt on Thu Mar 31 2016 18:34:39 GMT+0000 (UTC)
@whyrusleeping How would you do this? Or @dignifiedquire, do you know?
From @whyrusleeping on Sat Dec 10 2016 01:26:12 GMT+0000 (UTC)
The answer given by @lidel is correct.
From @alexanderattar on Tue Mar 07 2017 22:03:26 GMT+0000 (UTC)
Does anyone know what would cause the location to be unknown? I set up a remote node and using the tool @lidel gave above (http://freegeoip.net/json/), I have confirmed that the IP location is in New York, but when I visit the webui on the node info page, I see that the location is unknown, and that the node is also not connected to any peers. I’m wondering if I’ve missed something as far as configuration goes. Thanks in advance!
From @Kubuxu on Tue Mar 07 2017 22:06:14 GMT+0000 (UTC)
The GeoIP database we use was not updated for a long time so some IPs might have wrong/unknown locations.
If you are getting no peers it might be NAT/firewall configuration problem. There are other issues on that too.
From @alexanderattar on Wed Mar 08 2017 17:18:31 GMT+0000 (UTC)
Ah okay. Thanks for the response @Kubuxu! That sounds like it could be the cause of the unknown location. I do not have any firewall at the moment so the node should be open for connections. I am able to see peers in the console via ipfs swarm peers so perhaps it is just an issue with the webui? I can open a new issue if that seems to be the case.
Hi there,
Any update about this, I’m curious about that, too. It seems like IPFS doesn’t use ipfs-geoip to detect location any more. I’m not able to search code related to ipfs-geoip module in go/javascript client. And in white paper, I also could not find any information about how IPFS detect node location.
Thanks.
ipfs-geoip is still used (if you are looking at the actual running UI in your browser, the code is minified, so it may not be easy to identify). Here’s where it is in the WebUI source: https://github.com/ipfs-shipyard/ipfs-webui/blob/master/src/js/pages/connections.js
However, if you take a look at the blame view in the ipfs-geoip source, you can see that the copy of the GeoIP database being used hasn’t been updated in more than two years: https://github.com/ipfs/ipfs-geoip/blame/master/src/generate/index.js#L20
I looks like ipfs-geoip is only used for getting location from peer IP address and displaying in webui only. It’s a project from community, not from IPFS org, so I don’t think ipfs-geoip is used anymore.
That’s correct — the WebUI is all ipfs-geoip has ever been used for. An IPFS node doesn’t really have any concept of geographic location and never has.
It’s a project from community, not from IPFS org, so I don’t think ipfs-geoip is used anymore.
Just to be clear, even though the WebUI is in ipfs-shipyard, that is the source code for the app you get when loading http://localhost:5001/webui in your local gateway. Technically, it doesn’t ship as part of go-ipfs (it loads on demand from the network), but it is an officially supported part of IPFS.
freegeoip is no longer free nor working as it’s been replaced by ipstack.com