[tor-bugs] #16255 [Tor]: Guardfraction on dirauths screws up bandwidth weights

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

#16255: Guardfraction on dirauths screws up bandwidth weights
-----------------------------------+------------------------------------
 Reporter:  asn                    |          Owner:
     Type:  defect                 |         Status:  new
 Priority:  normal                 |      Milestone:  Tor: 0.2.6.x-final
Component:  Tor                    |        Version:
 Keywords:  tor-dirauth tor-guard  |  Actual Points:
Parent ID:                         |         Points:
-----------------------------------+------------------------------------
 It seems that dirauths stopped including bandwidth weights on the
 consensus after Guardfraction got enabled:
 https://lists.torproject.org/pipermail/tor-dev/2015-June/008908.html

 Looking at weasel's dirauth we get plenty of related error messages:
 {{{
 [warn] Bw Weights error 1 for Case 3be (E scarce, Wee=1, Wmd == Wgd) v10.
 G=14793673 M=8310679 E=3428814 D=7040272 T=26698303 Wmd=-512 Wme=0
 Wmg=2192 Wed=11025 Wee=10000 Wgd=-512 Wgg=7808 Wme=0 Wmg=2192
 weight_scale=10000
 }}}

 That is, it seems like the bandwidth calculation of the dirauths got
 screwed a bit. This might be the result of using the guardfraction data
 during bandwidth calculation in `compute_weighted_bandwidths()` that might
 combine badly with #13297.

 The negative Wmd/Wgd values seem weird here as well.

 Let's disable the GuardFraction feature for now, till we figure out this
 issue.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16255>
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