Tor relay on Debian 12, not logging bootstrap process

So, I’ve setup my relay on a Debian Bookworm system. When I start Tor, this is what gets logged to the system journal

Blockquote
eb 16 18:50:44 thindebian tor[416048]: Feb 16 18:50:44.122 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Feb 16 18:50:44 thindebian tor[416048]: Feb 16 18:50:44.122 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Feb 16 18:50:44 thindebian tor[416048]: Feb 16 18:50:44.122 [notice] Read configuration file “/etc/tor/torrc”.
Feb 16 18:50:44 thindebian tor[416048]: Feb 16 18:50:44.126 [notice] You configured a non-loopback address ‘192.168.1.2:9053’ for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Feb 16 18:50:44 thindebian tor[416048]: Feb 16 18:50:44.126 [notice] Based on detected system memory, MaxMemInQueues is set to 5537 MB. You can override this by setting MaxMemInQueues by hand.
Feb 16 18:50:44 thindebian tor[416048]: Configuration was valid
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.307 [notice] Tor 0.4.8.10 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.307 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.308 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.308 [notice] Read configuration file “/etc/tor/torrc”.
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.312 [notice] You configured a non-loopback address ‘192.168.1.2:9053’ for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.312 [notice] Based on detected system memory, MaxMemInQueues is set to 5537 MB. You can override this by setting MaxMemInQueues by hand.
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] You configured a non-loopback address ‘192.168.1.2:9053’ for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] Opening DNS listener on 192.168.1.2:9053
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] Opened DNS listener connection (ready) on 192.168.1.2:9053
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] Opening OR listener on [2600:4040:3037:e600::1c28]:9001
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] Opened OR listener connection (ready) on [2600:4040:3037:e600::1c28]:9001
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] Opening OR listener on 192.168.1.2:9001
Feb 16 18:50:44 thindebian tor[416049]: Feb 16 18:50:44.316 [notice] Opened OR listener connection (ready) on 192.168.1.2:9001
Feb 16 18:51:22 thindebian systemd[1]: Started tor@default.service - Anonymizing overlay network for TCP.

Blockquote

and that’s it… I’m expecting to see the bootstrapping process, and it testing if im reachable, etc. but there’s nothing after this.

I checked Relay Search and it appears that my tor relay is showing as up and operational… (but my ipv6 address isn’t showing up, even though I have confirmed access… but since I’m not seeing the bootstrap process, I’m not seeing the usual “checking if your ip is reachable” message…

Anyone know why I’m not seeing anything further in the debian journal?

Here is my current torrc file

Blockquote
Nickname MTGRIRelay
ORPort [2600:4040:3037:e600::1c28]:9001
ORPort 192.168.1.2:9001
Address tor.mytechguyri.com
ExitRelay 0
IPv6Exit 0
DirCache 1
GeoIPFile /usr/share/tor/geoip
Log info syslog
VirtualAddrNetwork 10.192.0.0/10
AutomapHostsOnResolve 1
DNSPort 192.168.1.2:9053
PathsNeededToBuildCircuits -1
DormantOnFirstStartup 0
RunAsDaemon 0
DataDirectory /var/lib/tor
PidFile /run/tor/tor.pid
AvoidDiskWrites 1
PublishServerDescriptor 1
User debian-tor
ExtendByEd25519ID auto
KeepBindCapabilities auto
ContactInfo John

Blockquote

1 Like

You configured an internal IPv4 address as ORPort:

I guess that’s why the connectivity check is skipped. Try to configure your public IPv4 address here.

The IPv6 address is a public one, but Tor doesn’t do connectivity checks on IPv6 addresses.

1 Like

I’m behind a NAT so it has to bind to that port… So I have since added a ORport mypublicip NoListen entry and added NoAdvertise to the 192.168.1.2 entry

According to the tor relay check it’s online and functioning, and both ip4 and ip6 addresses are seen… Still not sure why none of the bootstrap or connectivity checks show In the logs though

1 Like