2 ms·
So, in a private ipfs network (connect to other peers who have a shared secret key) https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#pr
by alexsicart 9y ago
So, in a private ipfs network (connect to other peers who have a shared secret key) https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#private-networks https://github.com/ipfs/go-ipfs/blob/master/docs/experimenta.... All the IPFS nodes are connected by default? Each peer pin files from other peers?
- StavrosK 9y agoNo, if I understand correctly, he just bootstraps the nodes from each other, making sure they are initially strongly connected. I tried that too, but it didn't reliably help the problem.
- prophesi 9y agoYep, precisely! And if I'm having peer discovery issues with just two nodes, I can't imagine what you guys are having to go through. :/ For the curious: you'd run `ipfs id` on the nodes to get their addresses. Then you'd run `ipfs config edit` on them and add the other node's address to the bootstrap section. https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#bootstrap https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#b... But yeah... They'd still mysteriously not connect to each other at times.
- StavrosK 9y agoYep :( It's pretty disheartening to work on a product for some time and have the underlying technology just not work up to your standard. Hearth is basically hit and miss for that reason, sometimes files show up right away and it's amazing, sometimes they time out and it's useless. Very frustrating, and there's absolutely nothing we can do about it.