Package: dhtnode Version: 1.3.4-3 Severity: important Tags: upstream dhtnode defaults to connecting to bootstrap.ring.cx, which has both an IPv4 and an IPv6 address. However, it apparently insists on trying to connect to the IPv6 address, even from systems like mine that still lack v6 connectivity, and the resulting frequent retries lead to a lot of syslog spam.
Although I agree that my ISP should get with the times ;-), dhtnode should meanwhile handle connection problems more gracefully. Specifically, it should fall back on IPv4 if it can't get IPv6 to work, and if neither works, it should pause for longer between retries, perhaps with an exponential backoff. Could you please look into it? Thanks! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dhtnode depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii libargon2-0 0~20161029-1 ii libc6 2.24-12 ii libgcc1 1:7.1.0-9 ii libgnutls30 3.5.14-2 ii libnettle6 3.3-1+b1 ii libreadline7 7.0-3 ii libstdc++6 7.1.0-9 dhtnode recommends no packages. dhtnode suggests no packages. -- no debconf information
