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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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):

 Replying to [comment:1 teor]:
 > You removed the log line where the relay guesses its own IPv4 address.
 Since self-testing to the ORPort was successful, I'm going to assume that
 it guessed x.x.x.x. You might want to set "Address x.x.x.x" if x.x.x.y is
 also a public IP address. (I'm guessing it's not, because you have a
 control port on it.)
 >

 Did have `Address` set.  Unabridged output posted next above.

 > It looks like Tor isn't launching the DirPort self-test, but it is
 waiting for the DirPort self-test to be successful before it publishes.
 Oops!
 >
 > Does this config work with Tor 0.3.3?

 No idea, did not try it.  Only just thought of trying this due to some
 DirPort abuse activity.  Tor-Relays:
 https://lists.torproject.org/pipermail/tor-relays/2018-May/015253.html

 > Does it work with Tor 0.2.9?
 > (If it does, we must fix this regression before 0.3.4 stable. If it has
 been a bug for a long time, maybe it can wait.)

 Doubt it but don't know.  Worked around the abuse with a rate-limit and
 don't need a backport, but this seems like a useful config for the future.

 >
 > I would normally ask "Does this config work if you don't set NoAdvertise
 on the DirPort?"
 > But the config probably won't work, because the relay will either guess
 x.x.x.x or x.x.x.y as its address, so one of the ORPort or DirPort checks
 will fail.

 Does work, running now.  Explicit Address config from the get-go.

 >
 > Does this config work if you set "DirPort x.x.x.x:d"?
 > Does this config fail if you set "DirPort x.x.x.x:d NoAdvertise"?

 With the above two, yes does work but with x.x.x.y as the NoAdvertise
 address.  Have been configuring an inside-network DirPort awhile now for
 some scripts that utilize consensus documents.

 >
 > Does this config work if you don't set a DirPort?

 Probably, but didn't try that.  Standard default setup, right?

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

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs