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 the
switches).
The command should probably output the help when called without arguments.
BR
Martin
On 09.03.24 14:55, marty1885 wrote:
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 much IO. While I was expecting at least hundreds of Kbps from experience
in the past.
How can I connect to the network? Please let me know what information I can
provide to diagnose the issue.
Best,
Martin
