Hi, I do not want to stop you from anything, but gnunet master is currently a pain to use.\ We have recently merged a CORE rewrite that fixes the crypto in the authenticated key exchange, but that makes it incompatible with any current releases. This includes the bootstrap peer. We do have a development bootstrap peer, but that is not enabled by default, and is not always running. You can try
$ gnunet-config -s hostlist -o SERVERS -V https://bootstrap.gnunet.org/development and restart you peer. Unfortunately, gnunets connectivity is still a mess right now because of the issues in the underlying subsystem(s), primarily transport. So, unless somebody finds time to actually fix those you will find it quite frustrating to use is my guess. Both maintainers probably do not have any time in the near future to address this. We badly need to stop slapping on new features and get this fixed asap, which I hope we can do within the year, but that is optimistic. Best Martin On Tue, 2025-09-09 at 16:01 +0000, k via Mailinglist for GNUnet developers wrote: > > Hello, > > After reading some documentation, I have the impression that it is > important to use a decent configuration file. > > Could somebody help me with writing a configuration file that gives > the highest chance for a working GNUNET without having the ability to > modify the router settings? > > My main issue is that I do not have any output, until now never had > when running this command: > > gnunet-core -s -c ~/.config/gnunet.conf > > Best Regards, > > > > > > >
