Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geoip database used on Peers page is out of date #1249

Closed
lidel opened this issue Oct 11, 2019 · 1 comment · Fixed by #1675
Closed

Geoip database used on Peers page is out of date #1249

lidel opened this issue Oct 11, 2019 · 1 comment · Fixed by #1675
Assignees
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@lidel
Copy link
Member

lidel commented Oct 11, 2019

Latency does not match Location

I recently noticed faster-than-speed-of-light connections to nodes in US:

ipfs-2019-10-11--15-07-26

geoip-wut-2019-10-11--15-05-19

(Ping from Poland to the USA should be 100ms or more)

dataset bundled with ipfs-geoip is out of date

I was not sure if we implemented FTL transport in libp2p (yet), so my second guess was that geoip database is out of date, and a manual check using https://www.maxmind.com/en/geoip-demo?pkit_lang=en confirmed the IP is now assigned to Germany (which explains low ping):

2019-10-11--15-08-21

I believe this should be addressed upstream (see my notes in both):

@lidel lidel added the kind/bug A bug in existing code (including security flaws) label Oct 11, 2019
@lidel lidel self-assigned this Oct 19, 2020
@lidel
Copy link
Member Author

lidel commented Oct 19, 2020

Upstream fix being prepared in ipfs-shipyard/ipfs-geoip#80

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant