[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: network from scratch

From: t3sserakt
Subject: Re: network from scratch
Date: Tue, 1 Nov 2022 13:58:14 +0000


Message: 2
Date: Mon, 31 Oct 2022 15:45:15 +0000
To: Martin Schanzenbach <>
Subject: Re: network from scratch
Message-ID: <Y1/>
Content-Type: text/plain; charset=us-ascii

Aha so adding -f to the gnunet-peer -s -g makes it output the hello.
Without -f it also outputs a hello, but not a friends hello.
And that URI is accepted by gnunet-peer -p
Did not verified it in the code, but maybe in F2F only friends hellos will be added.
Now the peer is listed with gnunet-peer (-f)

Now peer A and B has both peer A and B in their peerinfo lists.

However, the peer A is still not being sent by the hostlist (after retstarting
the nodes), still only the Y924 is being sent.
I assume friend hellos will not be send by the hostlist server.
Then I changed the URIs from gnunet://hello-friend to gnunet://hello.
Now the peers get sent with the hostlist.
Yes, but it is not a friend hello.
However, peer B still does not connect to peer A during bootstrap, in spite of
getting the peer info.
Because it is not a friend hello?
Also of note:

1. If I restart the peer A, again only Y924 is seems to be
left in the peerinfo db - that is, only Y924 is being sent to B.

2. After achieving connection, if I restart the nodes they don't
reconnect automatically.

I do not understand atm why the friend hello wasn't persisted. But maybe the hello send by the hostlist server was not persisted, because it was no friends hello.

Or maybe the hello was persited, but will not be listed in F2F mode?

Attachment: OpenPGP_0x524982A0100F7490.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]