Hi all,
I've just built and installed the new GNUnet 0.21. But my node isn't connected
to any peer after hours of waiting. Running gnunet-core shows no node is
connected to me.
```
❯ gnunet-core
(no output)
```
I have also checked `iotop` and can confirm gnunet-service-transport isn't
doing m
Hi,
the behaviour of gnunet-core changed. You can check the new switches
with --help.
Long-term core connections are know to be problematic behind NATs, still.
But with a freshly started peer, "gnunet-core -i" should give you your
peer id, "gnunet-core -s" the connections (you can also combine
Thanks for the reply.
I tried a few commands and still feels like my node is really not connected.
DHT can't put, NSE returns a very small network size and GNS cannot resolve.
Is this expected?
```
❯ gnunet-core -si
Current local peer identity:
CCXHBE49GRQVFAVFQ3BXVXPHHD63NG6ZNY31R0F59KVDZQA42
Hi,
what does gnunet-arm -I output? Are all of the services running?
For example, the peerstore database layout changed, so you probably have
to delete your old database ($HOME/.local/share/gnunet/peerstore/sqlite.db).
The road to a stable TNG will also be bumpy, so we rely on reports such
as
