Hello, please be patient. It will also help to delete your peerstore/gnunet user directory. The errors you see is indeed because a lot of HELLOs will not be invalid, since we require the addresses to be sorted. The new CORE handshake is still a bit unstable, there may be a lot of bugs which we will find over the course of the next weeks and hopefully fix in .1.
BR Martin On Mon, 2025-09-22 at 17:27 +0200, Noé Lopez via Mailinglist for GNUnet developers wrote: > Hi, > > I’ve updated my gnunet installation to 0.25.0, but I’m not getting > any > connections (gnunet-core -s is empty). > > I checked the logs and the only suspicious thing I could find was a > lot > of these messages: > > > 2025-09-22T16:57:38.276450+0200 transport-10082 WARNING External > > protocol violation detected at ../gnunet- > > 0.25.0/src/lib/hello/hello-uri.c:582. > > 2025-09-22T16:57:38.276454+0200 transport-10082 WARNING HELLO > > cannot be parsed! > > > 2025-09-22T16:57:35.245679+0200 peerstore-10072 ERROR Assertion > > failed at ../gnunet-0.25.0/src/lib/hello/hello-uri.c:422. > > 2025-09-22T16:57:35.245710+0200 peerstore-10072 ERROR Unable to > > parse HELLO message > > > 2025-09-22T16:56:30.956343+0200 hostlist-9833 WARNING External > > protocol violation detected at ../gnunet- > > 0.25.0/src/lib/hello/hello-uri.c:582. > > 2025-09-22T16:57:35.345410+0200 hostlist-10070 WARNING External > > protocol violation detected at ../gnunet- > > 0.25.0/src/lib/hello/hello-uri.c:582. > > > 2025-09-22T16:56:31.521686+0200 gnunet-daemon-topology-9840 WARNING > > External protocol violation detected at ../gnunet- > > 0.25.0/src/lib/hello/hello-uri.c:582. > > I assume this means that the other peers that my peer tries to > connect > to have incompatile versions, but I would expect to find at least a > few > people, especially at a time where 0.25.0 should be compatible with > master. > > Is the issue something else? Any ideas on how I can get connections > again? > > Thanks, > Noé Lopez
