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

Update to latest IPFS version - changes and testing needed #485

Closed
makew0rld opened this issue Apr 15, 2020 · 6 comments
Closed

Update to latest IPFS version - changes and testing needed #485

makew0rld opened this issue Apr 15, 2020 · 6 comments
Assignees

Comments

@makew0rld
Copy link
Contributor

Discussed in chat here.

I asked some questions about issues I think we'd encounter in ipfs/kubo#7109, starting here.

@makew0rld
Copy link
Contributor Author

I made a feature request that will enable nodes connected to the Internet and CJDNS to talk to CJDNS-only nodes: ipfs/kubo#7168.

@makew0rld
Copy link
Contributor Author

I've made a feature request concerning nodes connected to Yggdrasil as well, which poses a different problem: ipfs/kubo#7169

@makew0rld makew0rld self-assigned this Apr 17, 2020
@makew0rld
Copy link
Contributor Author

If they're direct routes, then we should consider them as LAN nodes for the purpose of the DHT, and things should crossed_fingers work out. https://github.com/libp2p/go-libp2p-kad-dht/blob/master/dht_filters.go#L142-L150
-- willscott

This applies Yggdrasil direct peers, and it definitely something we should test and verify. Also, what would happen to the connections that aren't direct, like two-hop peers, etc?

@makew0rld
Copy link
Contributor Author

v0.5.0 was released today, which supports only 2000::/3 being part of the IPv6 WAN. This solves any Yggdrasil issues.

I think we should upgrade, but disabling AutoNAT just in case. The main issue to be aware of is that nodes that are connected to the internet and the mesh will not be able to share files with the mesh. That is being tracked in ipfs/kubo#7168.

@makew0rld
Copy link
Contributor Author

makew0rld commented Jul 22, 2020

IPFS v0.5.1 and v0.6.0 have been out for a while. These changes should be looked at as well.

@makew0rld makew0rld changed the title Problems with upcoming IPFS v0.5.0 Update to latest IPFS version - changes and testing needed Jul 22, 2020
@makew0rld
Copy link
Contributor Author

IPFS v0.7 was released today. The default multihash encoding has changed (Starts with Qm instead of k51) but that doesn't seem to be expected/hardcoded anywhere so it should be fine.

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

2 participants