[tor-bugs] #26136 [Core Tor/Tor]: DirPort reachability test inconsistency when only "DirPort x.x.x.x:x NoAdvertise" configured

[Tor Bug Tracker & Wiki]

#26136: DirPort reachability test inconsistency when only "DirPort x.x.x.x:x
NoAdvertise" configured
----------------------------------------------+----------------------------
 Reporter:  starlight                         |          Owner:  (none)
     Type:  defect                            |         Status:
                                              |  needs_information
 Priority:  Medium                            |      Milestone:  Tor:
                                              |  0.3.4.x-final
Component:  Core Tor/Tor                      |        Version:  Tor:
                                              |  0.3.4.1-alpha
 Severity:  Normal                            |     Resolution:
 Keywords:  regression-maybe, 034-must-maybe  |  Actual Points:
Parent ID:                                    |         Points:
 Reviewer:                                    |        Sponsor:
----------------------------------------------+----------------------------

Comment (by starlight):

 relay does not guess it's own address:

 {{{
 Address x.x.x.x
 OutboundBindAddress x.x.x.x
 ORPort x.x.x.x:o
 DirPort x.x.x.y:d NoAdvertise
 ControlPort x.x.x.y:r
 }}}


 apologies, didn't think all the boot lines were needed, unabridged:

 {{{
 Tor 0.3.4.1-alpha (git-deb8970a29ef7427) running on Linux with Libevent
 x.x.x, OpenSSL x.x.x, Zlib x.x.x, Liblzma x.x.x, and Libzstd x.x.x.
 Tor can't help you if you use it wrong! Learn how to be safe at
 https://www.torproject.org/download/download#warning
 This version is not a stable Tor release. Expect more bugs than usual.
 Read configuration file "/home/tor/torrc".
 Your ContactInfo config option is not set. Please consider setting it, so
 we can contact you if your server is misconfigured or something else goes
 wrong.
 Scheduler type KIST has been enabled.
 Opening Control listener on x.x.x.y:r
 Opening OR listener on x.x.x.x:o
 Opening Directory listener on x.x.x.y:d
 Parsing GEOIP IPv4 file ./geoip.
 Parsing GEOIP IPv6 file ./geoip6.
 Configured to measure statistics. Look for the *-stats files that will
 first be written to the data directory in 24 hours from now.
 Your Tor server's identity key fingerprint is 'Unnamed
 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
 Bootstrapped 0%: Starting
 Starting with guard context "default"
 I learned some more directory information, but not enough to build a
 circuit: We have no usable consensus.
 I learned some more directory information, but not enough to build a
 circuit: We have no usable consensus.
 Bootstrapped 45%: Asking for relay descriptors
 I learned some more directory information, but not enough to build a
 circuit: We need more microdescriptors: we have 0/6476, and can only build
 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of
 exit bw = 0% of path bw.)
 I learned some more directory information, but not enough to build a
 circuit: We need more microdescriptors: we have 0/6476, and can only build
 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of
 exit bw = 0% of path bw.)
 Bootstrapped 50%: Loading relay descriptors
 Bootstrapped 55%: Loading relay descriptors
 Bootstrapped 60%: Loading relay descriptors
 Bootstrapped 65%: Loading relay descriptors
 Bootstrapped 70%: Loading relay descriptors
 Bootstrapped 75%: Loading relay descriptors
 Bootstrapped 80%: Connecting to the Tor network
 Bootstrapped 85%: Finishing handshake with first hop
 Bootstrapped 90%: Establishing a Tor circuit
 Tor has successfully opened a circuit. Looks like client functionality is
 working.
 Bootstrapped 100%: Done
 Now checking whether ORPort x.x.x.x:o is reachable... (this may take up to
 20 minutes -- look for log messages indicating success)
 Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not
 known. Closing.
 last message repeated 4 times
 Self-testing indicates your ORPort is reachable from the outside.
 Excellent.
 Performing bandwidth self-test...done.
 Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not
 known. Closing.
 last message repeated 17 times
 last message repeated 5 times
 Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not
 known. Closing.
 last message repeated 11 times
 last message repeated 11 times
 last message repeated 3 times
 Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not
 known. Closing.
 last message repeated 11 times
 last message repeated 10 times
 last message repeated 10 times
 Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not
 known. Closing.
 last message repeated 9 times
 Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not
 known. Closing.
 last message repeated 11 times
 last message repeated 11 times
 last message repeated 7 times
 Requested exit point '$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' is not
 known. Closing.
 last message repeated 11 times
 last message repeated 11 times
 last message repeated 11 times
 last message repeated 11 times
 last message repeated 10 times
 last message repeated 10 times
 last message repeated 10 times
 Your server (x.x.x.x:0) has not managed to confirm that its DirPort is
 reachable. Relays do not publish descriptors until their ORPort and
 DirPort are reachable. Please check your firewalls, ports, address,
 /etc/hosts file, etc.
 Your ContactInfo config option is not set. Please consider setting it, so
 we can contact you if your server is misconfigured or something else goes
 wrong.
 Opening Directory listener on x.x.x.x:80
 Catching signal TERM, exiting cleanly.
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26136#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online