nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-10 13:13:44 +01:00
Code Issues Packages Projects Releases Wiki Activity

Reduce fallback bandwidth requirement to 1 MByte/s

Browse Source
This commit is contained in:
teor 2016-12-07 15:58:57 +11:00
parent 35da99a712
commit 124c342364
No known key found for this signature in database
GPG Key ID: 450CBA7F968F094B
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
changes/fallbacks-201612
View File

@ -23,6 +23,8 @@
Closes ticket 20908.
- Allow 3 fallbacks per operator. (This is safe now we are choosing 200
fallbacks.) Closes ticket 20912.
- Reduce the minimum fallback bandwidth to 1 MByte/s.
Part of #18828.
o Minor bugfix (fallback directories):
- Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
Closes ticket 20877; bugfix on commit 9998343 in tor-0.2.8.3-alpha.

4
scripts/maint/updateFallbackDirs.py
View File

@ -191,12 +191,12 @@ MAX_FALLBACKS_PER_FAMILY = 3
EXIT_BANDWIDTH_FRACTION = 1.0
# If a single fallback's bandwidth is too low, it's pointless adding it
# We expect fallbacks to handle an extra 30 kilobytes per second of traffic
# We expect fallbacks to handle an extra 10 kilobytes per second of traffic
# Make sure they can support a hundred times the expected extra load
# (Use 102.4 to make it come out nicely in MByte/s)
# We convert this to a consensus weight before applying the filter,
# because all the bandwidth amounts are specified by the relay
MIN_BANDWIDTH = 102.4 * 30.0 * 1024.0
MIN_BANDWIDTH = 102.4 * 10.0 * 1024.0
# Clients will time out after 30 seconds trying to download a consensus
# So allow fallback directories half that to deliver a consensus