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

ipfs still kills routers #4

Open
victorb opened this issue May 16, 2019 · 2 comments
Open

ipfs still kills routers #4

victorb opened this issue May 16, 2019 · 2 comments

Comments

@victorb
Copy link
Member

victorb commented May 16, 2019

Currently, having troubles developing with bolivar as after 30 seconds (just 10 peers), the router provided by my ISP is forcing a restart.

Thought we would be able to avoid this problem by using ipfslite with low values for the connection manager, but seems that's not enough.

There is a long-standing issue to have this fixed in go-ipfs: ipfs/kubo#3320

@victorb victorb changed the title ipfs still killing routers ipfs still kills routers May 16, 2019
@victorb
Copy link
Member Author

victorb commented May 16, 2019

Thinking if we should change Bolivar to work over a private network instead, where Open-Registry and other Bolivar peers would be the only ones, might help with this issue. But it's a temporary solution.

@victorb
Copy link
Member Author

victorb commented May 16, 2019

https://github.com/open-services/bolivar/blob/master/p2p/p2p.go#L121 needs to use NewDHTClient instead of New to use DHT Client mode (I think) to see if it helps to not kill routers.

From ipfs/kubo#3320

Introduces the issue (again, I think) that we won't respond to DHT requests for other Bolivar peers. That's no fun.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant