Package: tor Version: 0.4.7.11-1~bpo11+1 Followup-For: Bug #998681 Dear Maintainer,
this bug still persists. As far it seems, tor service needs to be launched AFTER networking. (1) I solved the problem by modifying in file /usr/lib/systemd/system/tor@default.service After=network.target nss-lookup.target into After=network.target network-online.target nss-lookup.target I hope this can be useful. Many thanks in advance, Domenico NOTES (1) https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-0.deb11.2-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tor depends on: ii adduser 3.118 ii libc6 2.31-13+deb11u5 ii libcap2 1:2.44-1 ii libevent-2.1-7 2.1.12-stable-1 ii liblzma5 5.2.5-2.1~deb11u1 ii libseccomp2 2.5.1-1+deb11u1 ii libssl1.1 1.1.1n-0+deb11u3 ii libsystemd0 251.3-1~bpo11+1 ii libzstd1 1.4.8+dfsg-2.1 ii lsb-base 11.1.0 ii runit-helper 2.10.3 ii zlib1g 1:1.2.11.dfsg-2+deb11u2 Versions of packages tor recommends: ii logrotate 3.18.0-2+deb11u1 ii tor-geoipdb 0.4.7.11-1~bpo11+1 ii torsocks 2.3.0-3 Versions of packages tor suggests: ii apparmor-utils 2.13.6-10 pn mixmaster <none> pn nyx <none> pn obfs4proxy <none> pn socat <none> ii torbrowser-launcher 0.3.3-6
