makeworld

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

> 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](https://github.com/ipfs/go-ipfs/issues/7169#issuecomment-615009202) This applies...

v0.5.0 [was released today](https://github.com/ipfs/go-ipfs/releases/tag/v0.5.0), 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....

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

IPFS [v0.7](https://github.com/ipfs/go-ipfs/releases/tag/v0.7.0) 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.

This should only require a docs update, right?

> We need a way of identifying each packet so that a node knows if they already received once and it came back, or if its a new one that...

I feel like nodeexporter should handle live stats, and the tracking of those stats over periods of time, etc. Nodeinfo should hold mostly static information that's important to have accessible,...

@benhylau I agree with you that sticking to the spec is best. I didn't do it at first, but I see how it makes more sense now. And yes a...

I believe IPFS nodes exchange ids anyway, verifying that they match public keys and things. I don't think it should be an issue.