Re: DNS/IP of firefly.gnunet.org and v21.gnunet.org

I think it may be necessary to purge the peerstore of all peers that 
know the old HELLO as well.
In any case, we'll look into that asap.
We may have to create a new peer identity.
The primary issue with the bootstrap hello is that it does not expire.

Br

On 30.07.24 17:40, ToBo wrote:
> Hi,
> 
> wouldn’t it be enough to exchange the HELLO send bei v21.gnunet.org with a correct one?
> 
> 
>> 30 juli 2024 kl. 17:37 skrev Schanzenbach, Martin <[email protected]>:
>>
>> Hello,
>>
>> sorry for the late reply.
>> Right, very recently all the IPs of our bootstrapping peer changed (over which 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:
>>> 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.218 but the current IP is 193.5.87.218 or 193.5.87.219.. similar for IPv6. Also the reverse DNS mapping is also irritating. Also the HELLO that is loaded from v21.gnunet.org seems to contain wrong IPs.
>>> regards
>>
> 
>