Re: [GNUnet-developers] Network size issues

[Christian Grothoff]

Hi!

Thanks for the head's up. That was a double whammy: I failed to set the
hostlist daemon's port correctly, that's why the hostlist was down.

At the same time, given that we lost /home, we lost the original private
key of the hard-coded bootstrap peer, which was the 2nd strategy for
bootstrapping.

Without either of those, any peer that got disconnected (or freshly
started) wouldn't be able to connect to the network at all anymore.

i suspect your singular 'tum.de' connection didn't even go properly up,
it was just the peer trying to talk to the peer that no longer existed
(and talking to the new peer, failing to connect, disconnecting,
reconnecting, etc.).

Anyway, I've fixed the hostlist now, the next release will contain the
new public key of the sam peer, and hopefully a 2nd hard-coded bootstrap
peer as well.

Thanks for the heads-up!

-Christian

On 4/25/19 5:43 PM, IC Rainbow wrote:
> Hi!
> 
> I happen to run a node that collects network size estimation stats and
> noticed it went to mere 40s circa recent server flops:
> https://imgur.com/a/e1ZdAd6
> 
> At the same time some of my nodes started having troubles with
> hostlist downloading and now stuck with a singular tum.de connection.
> 
> _______________________________________________
> GNUnet-developers mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnunet-developers
>

signature.asc
Description: OpenPGP digital signature