aboutsummaryrefslogtreecommitdiff
path: root/changes/torrc_continuation
diff options
context:
space:
mode:
authorSebastian Hahn <sebastian@torproject.org>2010-09-30 06:10:56 +0200
committerSebastian Hahn <sebastian@torproject.org>2010-09-30 06:17:54 +0200
commit73def430e3ad3be0c9fe9accd4ebfc7a35e572b2 (patch)
treef245f568373990bfcc66865ff06ca25cd23f0e42 /changes/torrc_continuation
parent45c51e32385d6f3c3eaefcab4927a50d1968d437 (diff)
downloadtor-73def430e3ad3be0c9fe9accd4ebfc7a35e572b2.tar
tor-73def430e3ad3be0c9fe9accd4ebfc7a35e572b2.tar.gz
Use an upper and lower bound for bridge weights
When picking bridges (or other nodes without a consensus entry (and thus no bandwidth weights)) we shouldn't just trust the node's descriptor. So far we believed anything between 0 and 10MB/s, where 0 would mean that a node doesn't get any use from use unless it is our only one, and 10MB/s would be a quite siginficant weight. To make this situation better, we now believe weights in the range from 20kB/s to 100kB/s. This should allow new bridges to get use more quickly, and means that it will be harder for bridges to see almost all our traffic.
Diffstat (limited to 'changes/torrc_continuation')
0 files changed, 0 insertions, 0 deletions