ich we had no control).
> That will impact the bootstrapping of our peer and (of course) make the HELLO
> that ships with gnunet invalid.
>
> Unfortunately, there is not much we can do right now until the next release.
>
> BR
> Martin
>
> On 30.07.24 17:30, ToBo wrote:
&g
Hi,
I have found out why a freshly installed 0.21.2 does not connect to the
infrastructure. The DNS mapping of v21.gnunet.org and firefly.gnunet.org on the
one side and the HELLO of EFBZMC2ME.. stored in the src tree does not work.
Among other things the HELLO does contain the IP 147.87.255.21
Hi,
I try to get "gnunet-core v0.21.2 release” to run. But "gnunet-core -s” remains
empty even after hours. The log is showing some kind of network problem with
gnunet. The network is otherwise working without any problems. What is the
problem here?
2024-07-28T14:02:10.618566+ cadet-2700
Hi,
> 29 juli 2022 kl. 22:58 skrev Martin Schanzenbach :
> Excerpts from ToBo's message of 2022-07-29 14:23:48 +0200:
>> I set up a three nodes in a very simple configuration: A and B is behind
>> NAT, so they both have to communicate with each other through C
>>
>> A -> C <- B
>>
>> Al
Hi,
I set up a three nodes in a very simple configuration: A and B is behind NAT,
so they both have to communicate with each other through C
A -> C <- B
All nodes are in friend only mode. All nodes have some knowledge of each other,
at least you can see infos in "gnunet-peerinfo" or "g
