Hello, Aaron M. Ucko writes:
> Petter Reinholdtsen <p...@hungry.com> writes: > >> I guess someone should test and figure out what the status is. The >> latest opendht is in Debian unstable and testing now. > > As of 2.4.10-1, it no longer floods logs, but it doesn't seem to have > found anything either: > > $ dhtnode > OpenDHT node [...] running on port [...] > (type 'h' or 'help' for a list of possible commands) > > >> ll > OpenDHT node [...] running on port [...] > >> 1 ongoing operations > Storage has 0 values, using 0 KB > IPv4 stats: > Known nodes: 0 good, 0 dubious, 0 incoming. > 0 searches, 0 total cached nodes > > IPv6 stats: > Known nodes: 0 good, 0 dubious, 0 incoming. > 0 searches, 0 total cached nodes > > Meanwhile, all I see in the log is > > dhtnode[...]: Bootstrap: bootstrap.ring.cx > > Thanks for asking! Have you tried specifying a bootstrap node explicitly with '-b'? bandali@sid:~$ dhtnode -b bootstrap.jami.net Bootstrap: bootstrap.jami.net OpenDHT node 7b6381a7314777d658e17e9cbd3938453a340294 running on port 47742 (type 'h' or 'help' for a list of possible commands) >> ll >> OpenDHT node 7b6381a7314777d658e17e9cbd3938453a340294 running on port 47742 1 ongoing operations Storage has 28 values, using 47 KB IPv4 stats: Known nodes: 10 good, 8 dubious, 1 incoming. 1 searches, 50 total cached nodes Routing table depth: 3 Network size estimation: 64 nodes IPv6 stats: Known nodes: 0 good, 7 dubious, 0 incoming. 0 searches, 8 total cached nodes Considering the various connectivity improvements in the recent and earlier releases since this bug was originally filed, and also that the forwarded copy of the was closed upstream, I suggest we close this bug here on the BTS as well. Best, -a
