#17147: long-running client path-selection not seeing some (fast) exit nodes ---------------------------+------------------------------- Reporter: starlight | Owner: Type: defect | Status: needs_information Priority: normal | Milestone: Tor: 0.2.??? Component: Tor | Version: Tor: 0.2.6.10 Resolution: | Keywords: Actual Points: | Parent ID: Points: | Sponsor: ---------------------------+-------------------------------
Comment (by starlight): >What is EntryNodes set to? Not willing to reveal my guard. Is a single high-quality, long-running guard running 0.2.6.10. >Is StrictNodes set? No, but don't have ExcludeNodes set so what difference would it make? Issue is that for days a new high-weight exit was not selected by the normal routing algorithm and the new exit was refused as a choice when an attempt was made to force it. Should have traced this when it happened but it so surprised me I didn't think of it. Have a script to enable debug tracing for the next time I see it, but I turned UseMicrodescriptors back on since its misbehavior bothers me less than this issue. Can put back UseMicrodescriptors 0 and try to reproduce with debug tracing if desired. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17147#comment:3> 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