*Update:* If I launch gnunet-core -m, from time to time I see a key sent message for peers GKZS and VAY0. But it seems these peers don't like me.
--madmurphy On Sun, Oct 13, 2024 at 1:59 PM madmurphy <madmurphy...@gmail.com> wrote: > Thank you Martin. I have been periodically monitoring it since yesterday, > and it seems that it never goes beyond something like this single line: > > Sun Oct 13 13:53:23 2024: connection established DESN (timeout in > 299 s) > > In general the string on the right (which I guess is the identity of the > peer I am connected to) is always DESN. Shouldn't I see at least you and > Christian and someone else? > > --madmurphy > > On Sun, Oct 13, 2024 at 12:53 PM Martin Schanzenbach <schan...@gnunet.org> > wrote: > >> gnunet-core -s returns all your active connections or connection >> requests, similar to what gnunet-peerinfo did before. >> If it is only a single line you are only connected (or connecting) to >> that single peer. >> >> For me right now, the output is: >> >> Sun Oct 13 13:50:17 2024: connection established DESN (timeout in 290 s) >> Sun Oct 13 13:50:17 2024: connection established GKZS (timeout in 297 s) >> >> BR >> >> On Sun, 2024-10-13 at 12:16 +0100, madmurphy wrote: >> >> I have missed the last changes in GNUnet, so I apologize if I have to >> catch up. Is it normal that gnunet-core -s returns only one line (which >> says that I have established a connection and not much else)? >> >> When there was gnunet-peerinfo(-gtk) I would normally see several peers I >> was connected to. >> >> --madmurphy >> >> >>
