You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.
When one of the positions has 0 bandwidth, which can happen in small Tor networks, Tor fails to produce weights in the consensus footer which causes it to default to an older path selection algorithm.
As stated in the threads, if you use the strict flag assignment feature that I proposed in https://trac.torproject.org/projects/tor/ticket/14882 and was merged into Tor 0.2.7 stable, then we can set the flags properly to avoid running into this issue.
The text was updated successfully, but these errors were encountered:
When one of the positions has 0 bandwidth, which can happen in small Tor networks, Tor fails to produce weights in the consensus footer which causes it to default to an older path selection algorithm.
I proposed a fix in Tor here:
https://trac.torproject.org/projects/tor/ticket/14881
More info about this bug, see these mailing list threads:
http://mailman.cs.umn.edu/archives/shadow-support/2015-November/000462.html
http://mailman.cs.umn.edu/archives/shadow-support/2015-December/000465.html
As stated in the threads, if you use the strict flag assignment feature that I proposed in https://trac.torproject.org/projects/tor/ticket/14882 and was merged into Tor 0.2.7 stable, then we can set the flags properly to avoid running into this issue.
The text was updated successfully, but these errors were encountered: