Hello Jacki, On 25/08/2020 11:50, TheJackiMonster wrote:
as far as I know you don't need to be connected to as many peers as possible. For many services it won't really matter to reach specific peers.
I suppose so, yes - but I would still expect to "see" more than 5 nodes... Is gnunet-peerinfo providing more peers for you? It is 2 days that I run gnunet now, but still didn't learn of any other peer, and gnunet-search is still unable to find any file on the network. Is gnunet-search working for you? (I mean - does it return any result for any possible query?) I also tried publishing a random file of few KBs just to see how it goes, but this is also stuck since yesterday.
If you want to establish connections to specific peers you can do this using the hello-string which you can optain with `gnunet-peerinfo -g` from your own peer and others can use it with `gnunet-peerinfo -p $HELLO_STRING`.
That would be nice - and maybe I'd learn some other peers from that peer via DHT... Unfortunately, I do not know anybody on gnunet, so I am limited to using the public hostlists.
best, Mateusz
On Mon, 2020-08-24 at 17:04 +0200, Mateusz Viste wrote:Hello, I am trying to run gnunet, but my installation struggles at finding peers. peerinfo returns this: $ ./gnunet-peerinfo Peer `M11ETFR5QFZ8KKVHHEDKTKWZEW00QD50NZAKZB7965MTW6HNGGSG' Peer `FJMDCD66A71E340AHAZ641K8N1KQ54DSMJ212K817M9613BCTDDG' Expires: Tue Aug 25 05:00:09 2020 tcp.0.124.ip-51-178-50.eu:2086 Peer `V8XXK9GAN5ZJFRFQP8MQX3D83BZTSBQVHKWWD0JPE63Z821906EG' Expires: end of time tcp:12:0 Expires: end of time tcp:24:0 Expires: end of time http_client:34:0 Expires: end of time http_client:59:0 Expires: end of time https_client:35:0 Expires: end of time https_client:60:0 Peer `Y924NSHMMZ1N1SQCE5TXF93ED6S6JY311K0QT86G9WJC68F6XVZ0' Expires: end of time tcp.0.127.0.0.1:2086 Expires: end of time tcp.0.gnunet.in.tum.de:2086 Expires: end of time tcp.0.gnunet-stun.in.tum.de:2086 Expires: end of time tcp.0.172.18.0.1:2086 Expires: end of time tcp.0.172.17.0.1:2086 Expires: end of time tcp.0.172.20.0.1:2086 Expires: end of time tcp.0.172.19.0.1:2086 Expires: end of time tcp.0.172.22.0.1:2086 Expires: end of time tcp.0.[::1]:2086 Expires: end of time tcp.0.[sam.net.in.tum.de]:2086 Peer `DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0' Expires: end of time udp:10:0 Expires: end of time udp:10:0 Expires: end of time udp:22:0 Expires: end of time tcp.0.gnunet.in.tum.de:2086 Expires: end of time tcp.0.gnunet-stun.in.tum.de:2086 Expires: end of time tcp.0.[sam.net.in.tum.de]:2086 Expires: end of time tcp:12:0 Expires: end of time tcp:24:0 Expires: end of time http_client:34:0 Expires: end of time http_client:58:0 Expires: end of time https_client:35:0 Expires: end of time https_client:59:0 Peer `RM4WTVSQAA38GFK2D7NDC20KKNTXRTTVDW8F8VSFGTKDYX4BSZFG' Expires: Tue Aug 25 04:57:44 2020 tcp.0.104.152.211.250:2086 This is 5 peers in theory, but gnunet-statistics reports only 1 active tcp connection. This doesn't seem like much, right? I have enabled DHT peers discovery (OPTIONS = -b -e in hostlist section of the config file), but without improvement. I suppose gnunet is running on more than 5 computers. How could I add extra peers? Mateusz
