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

Connectivity issues in China #6660

Closed
IPSE-TEAM opened this issue Sep 23, 2019 · 3 comments
Closed

Connectivity issues in China #6660

IPSE-TEAM opened this issue Sep 23, 2019 · 3 comments
Labels
status/duplicate This issue or pull request already exists

Comments

@IPSE-TEAM
Copy link

The ip in China is not enough. The ip of our ipfs node is changing, but we update the changed peerid to bootstrap, but it is not good to find the peers I need to connect through the nodes in bootstrap. The main reason may be that the intranet penetrates NAT.

@IPSE-TEAM IPSE-TEAM added the kind/enhancement A net-new feature or improvement to an existing feature label Sep 23, 2019
@hsanjuan
Copy link
Contributor

hsanjuan commented Mar 6, 2020

Seems related to your other #6649 issue so I'm going to consolidate here.

There are major improvements coming to DHT (ability to find other dialable nodes) and using TLS instead of secio might improve connectivity. Stay tuned for v0.5.0 in the next few weeks.

@hsanjuan hsanjuan changed the title bootstrap peerid could not find peers Connectivity issues in China Mar 6, 2020
@hsanjuan
Copy link
Contributor

hsanjuan commented Mar 6, 2020

From the other issue:

We are the IPSE project party. In the past, our ipfs client dumped more than 1000 ipfs nodes distributed in mainland China to bootstrap, which can connect to most nodes, but recently, in this way, the basic connection is not To these seed nodes, the number of nodes connected to them has dropped significantly. Previously, they were able to connect to more than 1,000, and now they are at most 600, and most of them are distributed in North America and Europe. I suspect that after the ipfs node update version, the ability to NAT has dropped, and I hope to optimize this function.

@hsanjuan
Copy link
Contributor

hsanjuan commented Mar 6, 2020

Actually, let's consolidate this on #5993 which talks about the same. Other than that and waiting for v0.5.0 there are no actionables for this issue.

Thanks!

@hsanjuan hsanjuan closed this as completed Mar 6, 2020
@hsanjuan hsanjuan added status/duplicate This issue or pull request already exists and removed kind/enhancement A net-new feature or improvement to an existing feature labels Mar 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants