aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2010-08-15 04:01:42 -0400
committerRoger Dingledine <arma@torproject.org>2010-08-15 04:01:42 -0400
commit8d588e7b1a4fccffaa8318ed14d00a2ef615c53a (patch)
tree2c9580ada20875112cca1b120ade06d1f5a498fd /changes
parent2bc1842aaac1119a840b8ed3fa815c6f71053ac7 (diff)
downloadtor-8d588e7b1a4fccffaa8318ed14d00a2ef615c53a.tar
tor-8d588e7b1a4fccffaa8318ed14d00a2ef615c53a.tar.gz
reinit per-conn token buckets on config or consensus change
Diffstat (limited to 'changes')
-rw-r--r--changes/1830-token-buckets9
1 files changed, 9 insertions, 0 deletions
diff --git a/changes/1830-token-buckets b/changes/1830-token-buckets
new file mode 100644
index 000000000..923b8323f
--- /dev/null
+++ b/changes/1830-token-buckets
@@ -0,0 +1,9 @@
+ o Major bugfixes:
+ - The PerConnBWRate and Burst config options, along with the
+ bwconnrate and bwconnburst consensus params, initialized each conn's
+ token bucket values only when the connection is established. Now
+ update them if the config options change, and update them every time
+ we get a new consensus. Otherwise we can encounter an ugly edge
+ case where we initialize an OR conn to client-level bandwidth,
+ but then later the relay joins the consensus and we leave it
+ throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.