diff options
| author | Nick Mathewson <nickm@torproject.org> | 2021-03-17 08:45:37 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2021-03-17 08:45:37 -0400 |
| commit | 2ae24d003d1d12e8e202748c4398d7438e4a65d9 (patch) | |
| tree | ed28225754a655c069a9a6d5fd6b66af2fdfc205 /changes | |
| parent | 59bbf8cde9144ee5c8d060959e723a4bedfd6bb8 (diff) | |
| download | tor-2ae24d003d1d12e8e202748c4398d7438e4a65d9.tar.gz tor-2ae24d003d1d12e8e202748c4398d7438e4a65d9.zip | |
Add a MinTimeToReportBandwidth option; make it 0 for testing networks.
This option changes the time for which a bandwidth measurement period
must have been in progress before we include it when reporting our
observed bandwidth in our descriptors. Without this option, we only
consider a time period towards our maximum if it has been running
for a full day. Obviously, that's unacceptable for testing
networks, where we'd like to get results as soon as possible.
For non-testing networks, I've put a (somewhat arbitrary) 2-hour
minimum on the option, since there are traffic analysis concerns
with immediate reporting here.
Closes #40337.
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/ticket40337 | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/changes/ticket40337 b/changes/ticket40337 new file mode 100644 index 0000000000..f8f136a740 --- /dev/null +++ b/changes/ticket40337 @@ -0,0 +1,12 @@ + o Minor features (bandwidth reporting): + - Relays can now use the MinTimeToReportBandwidth option to change + the smallest amount of time over which they're willing to report + their observed maximum bandwidth. Previously, this was fixed + at 1 day. For safety, values under 2 hours are only supported on + testing networks. Part of a fix for ticket 40337. + + o Minor features (testing): + - Relays on testing networks now report their observed bandwidths + immediately from startup. Previously, they waited + until they had been running for a full day. Closes ticket + 40337. |