I tried to bootstrap that stuck peer from one of mine. Too bad the hello given by it contained a loads of link-local IPs and the peer table was properly confused, mixing keys and addresses between known (but unreachable) peers.
There should be somewhat trivial way to do this, like "tcp connect to this host:port, there's pkey waiting to introduce you to the network". Le ven. 26 avr. 2019 à 12:29, Christian Grothoff <[email protected]> a écrit : > Well, it'll make more sense to make anther release once firefly is up > with its own peer and we have some hostlist redundancy. And given that > the hostlist server is now configured correctly again, I see no urgency. > > A bigger question we need to study is whether we can do something else > to help peers bootstrap better when the hostlist(s) are unreachable. But > that's more long-term. > > On 4/26/19 12:42 AM, [email protected] wrote: > > Given the recent events, is there a need to make a release > > or do you think it's good as it is? > > _______________________________________________ > GNUnet-developers mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnunet-developers >
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
