View Issue Details

IDProjectCategoryView StatusLast Update
0011629GNUnetGNSpublic2026-07-20 14:39
ReporterJllx Assigned Toschanzen  
PrioritynormalSeverityblockReproducibilityalways
Status assignedResolutionopen 
Product Version0.27.0 
Summary0011629: can't bootstrap
DescriptionHi,
I'm testing gnunet on gentoo, I did build it from source, started "gnunet-arm -s" checked that services are available with "gnunet-arm -I"
so after I wanted to check if I was connected, so I done a "gnunet-gns -u gnunet.gns.alt" and it wait... wait... wait... and never timeout
so I done some wireshark capture to see if there was some firewall/NAT issue... and... nothing.... just regular ICMP some unrelated UDP trafic.

gnunet-config -s gns t
.gnunet.gns.alt = 000G0522TTKQESZ9KPRT2K0RA9ZC8YMD52D2XYVYVGPDCNPMWHH9QXXF4W
.pin.gns.alt = 000G0522TTKQESZ9KPRT2K0RA9ZC8YMD52D2XYVYVGPDCNPMWHH9QXXF4W
INTERCEPT_DNS = NO
MAX_PARALLEL_BACKGROUND_QUERIES = 1000
UNIX_MATCH_GID = YES
UNIX_MATCH_UID = NO
UNIXPATH = $GNUNET_RUNTIME_DIR/gnunet-service-gns.sock
BINARY = gnunet-service-gns
HOSTNAME = localhost
IMMEDIATE_START = YES
START_ON_DEMAND = YES

I wonder what is wrong....
TagsNo tags attached.

Activities

schanzen

2026-07-17 10:05

administrator   ~0029166

I need to investigate this, testing via GNS is probably not helpful, first it must be verified that you are actually connected and bootstrap via hostlist server(s) works. It is likely that due to recent urgent server updates the bootstrap peer is/was down for a prolonged period of time.

Jllx

2026-07-20 09:42

reporter   ~0029200

Hi, how can I help investigating?
there is no "troubleshoot" section in https://docs.gnunet.org/latest/users/start.html
if testing via GNS is not helpful what is the best way to see if the system is connected (seeing that the system is up is in the above docs)

pardon my ignorance, but I thought that gnunet rely on GNS and that without GNS, since we can't resolv hosts, there is no way to connect to the network.... are the bootstrap ip hardcoded?

schanzen

2026-07-20 10:43

administrator   ~0029201

GNUnet does not rely on GNS for bootstrapping. GNUnet needs so-called HELLO messages. A HELLO contains the Peer ID (public key) and a set of (signed) endpoints it can be reached at (e.g. TCP/IP addresses). Every installation ships with a single HELLO for our bootstrap peer. The bootstrap peer also collects known HELLOs of connecting peers and publishes them through a hostlist. Each client in its default configuration reads this hostlist and tries to connect to peers.

To check which peers are connected or your peer attempts to connect you can use the "gnunet-core" cli tool. For example "gnunet-core -m"

Jllx

2026-07-20 12:07

reporter   ~0029202

maybe that's my issue? is there a bootstrap peer file? maybe it wasn't installed?
will try the "gnunet-core -m" as soon as possible

schanzen

2026-07-20 12:11

administrator   ~0029203

The bootstrap file is downloaded via HTTP. Your problem likely was that our bootstrap peer was not running. I have restarted it the other day.

schanzen

2026-07-20 12:42

administrator   ~0029205

I just tested connecting with v0.28.0 and it seems we have a regression in our handshake crypto :( I will need to track down that bug fist I guess.

Jllx

2026-07-20 13:27

reporter   ~0029206

how can I re-download the file?(automatic or manually) maybe this should be added into installation documentation

schanzen

2026-07-20 14:39

administrator   ~0029207

You do not have to redownload anything. it is downloaded on ever new start of the peer and then regularly.

I found the regression and it works again (with git master HEAD).
On gnunet-core, the server outputs something like

Mon Jul 20 14:36:51 2026: Hello sent (I) PBM3 (timeout in 0 ms)
Mon Jul 20 14:36:51 2026: Done sent (I) PBM3 (timeout in 0 ms)
Mon Jul 20 14:36:51 2026: Done sent (I) PBM3 (timeout in 299 s)
Mon Jul 20 14:36:51 2026: Connected (I) PBM3 (timeout in 299 s)
Mon Jul 20 14:36:57 2026: Connected (I) PBM3 (timeout in 299 s)
Mon Jul 20 14:37:05 2026: Connected (I) PBM3 (timeout in 299 s)

For your client, you will probably only see the last line because it will have happened too fast, otherwise it will be stuck in any state above.
But you will have to upgrade first. Also, sometimes the bootstrap peer hangs, but that is an unrelated issue :/

Issue History

Date Modified Username Field Change
2026-07-12 01:45 Jllx New Issue
2026-07-17 10:04 schanzen Assigned To => schanzen
2026-07-17 10:04 schanzen Status new => assigned
2026-07-17 10:05 schanzen Note Added: 0029166
2026-07-20 09:42 Jllx Note Added: 0029200
2026-07-20 10:43 schanzen Note Added: 0029201
2026-07-20 12:07 Jllx Note Added: 0029202
2026-07-20 12:11 schanzen Note Added: 0029203
2026-07-20 12:42 schanzen Note Added: 0029205
2026-07-20 13:27 Jllx Note Added: 0029206
2026-07-20 14:39 schanzen Note Added: 0029207