Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:16:48Zhttps://gitlab.torproject.org/legacy/trac/-/issues/24110document control protocol router status format surprises when using microdesc...2020-06-13T15:16:48Zteordocument control protocol router status format surprises when using microdescriptorsIn Tor 0.3.0 (or earlier?), we made clients use microdescriptors by default. This changes the format of NS_CONTROL_PORT routerstatus lines, which breaks pytorctl, and therefore the bandwidth authorities.
Apparently, this issue can be re...In Tor 0.3.0 (or earlier?), we made clients use microdescriptors by default. This changes the format of NS_CONTROL_PORT routerstatus lines, which breaks pytorctl, and therefore the bandwidth authorities.
Apparently, this issue can be resolved by setting UseMicrodescriptors 0 or using 0.2.9.
edit: Let's update control-spec.txt to document the current (surprising) behavior and track further behavior improvements in other tickets.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/24045Measure and map overloaded or over-weighted relays2020-06-13T18:07:40ZteorMeasure and map overloaded or over-weighted relaysFrom #21394, it looks like some exits are allocated too much consensus weight, and then they fail.
Can we calculate and map or graph the bandwidth to consensus weight ratios of relays?
This would help us find out if the changes we make...From #21394, it looks like some exits are allocated too much consensus weight, and then they fail.
Can we calculate and map or graph the bandwidth to consensus weight ratios of relays?
This would help us find out if the changes we make are helping to allocate bandwidth more evenly.