#26136: DirPort reachability test inconsistency when only "DirPort x.x.x.x:x NoAdvertise" configured --------------------------+---------------------------------- Reporter: starlight | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Tor: unspecified Component: Core Tor/Tor | Version: Tor: unspecified Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------+---------------------------------- Changes (by teor):
* keywords: regression-maybe, 034-must-maybe => * status: needs_information => new * version: Tor: 0.3.4.1-alpha => Tor: unspecified * milestone: Tor: 0.3.4.x-final => Tor: unspecified Comment: Ok, then this is not a regression, because it has been around for a few releases. (Probably since 0.2.8 or 0.2.9 when the code was rewritten.) Here is a workaround: * run a separate Tor process with "DirPort x NoAdvertise" * if you have trouble with #23693 or similar errors, run a separate tor process with "DirPort x ORPort y PublishServerDescriptor 0" -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26136#comment:7> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs