Re: Cannot bootstrap GNUnet 0.21.0

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 resol=
ve.

Is this expected?

```
=E2=9D=AF gnunet-core -si
Current local peer identity: CCXHBE49GRQVFAVFQ3BXVXPHHD63NG6ZNY31R0F59KVDZQ=
A42PTG
(no further output)

=E2=9D=AF gnunet-dht-put -k "hello" -d "world" -e 40m
(hangs, this used to return almost immidately)

=E2=9D=AF gnunet-nse
1710047156276913 1.688203 0.755488 1.474102

=E2=9D=AF gnunet-gns -u gnunet.gns.alt -t PKEY
>>> Looking for `PKEY' records under `gnunet.gns.alt'
(no output)
```

On Saturday, March 9th, 2024 at 11:39 PM, Schanzenbach, Martin <schanzen@gn=
unet.org> wrote:

> Hi,
>=20
> 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=
.
>=20
> BR
> Martin
>=20
> On 09.03.24 14:55, marty1885 wrote:
>=20
> > Hi all,
> >=20
> > I've just built and installed the new GNUnet 0.21. But my node isn't co=
nnected to any peer after hours of waiting. Running gnunet-core shows no no=
de is connected to me.
> >=20
> > `=E2=9D=AF gnunet-core (no output)`
> >=20
> > I have also checked `iotop` and can confirm gnunet-service-transport is=
n't doing much IO. While I was expecting at least hundreds of Kbps from exp=
erience in the past.
> >=20
> > How can I connect to the network? Please let me know what information I=
 can provide to diagnose the issue.
> >=20
> > Best,
> > Martin